Refresh Servoy data after web data changed

Servoy Developer
Version R2 2.1rc3-build 306
Java version 1.4.2-38 (Mac OS X)

Database : MS SQL Server 2000
Hosted with an ISP

The SQL database controls user access to its data.
User access is controlled by a flag field within the user table of the database which allows it to be switched on & off at will.
The updates to this flag field are currently triggered from the LAN via a local Windows Service which sends an XML file to a webservice running on the website where the database is hosted.

The web service then modifies access based upon the contents of the XML

All this runs completely independently of Servoy.

I have now built a simple interface to that remote SQL database so that I can check the data myself and also assess how & when to move administration of the database from the Windows service & webservice to a Servoy solution.

I have noticed that data in the flag field which has been updated via the web service does NOT get reflected into my Servoy form until I close and reopen the solution or go into and out of design mode.

Forgive me if this has been asked before, but, how do I perform and / or control how and when the Servoy form data is refreshed ?

Thanks
Harry

If data is updated in the database through aother way than Servoy, and you want Servoy to reflect the datachanges, you have to refresh your viewed records so once in a while.

Servoy Caches all data, for better performance.

Under the database manager, there is a recordRefresh/recordRequery function. I forgot the exact name.

Search the forum for this topic. In the past it has been discussed extensively.

hope this helps,

Paul

Thanks for the tip, Paul.

i will check this out.

I did search for ‘refresh’ prior to posting and it did not turn up anything specific to my problem.

If anybody can point me to a thread or thread(s) I would appreciate it.

Harry

I did a forum search on refresh and got a lot of results… :shock:

Anyway, this post: http://forum.servoy.com/viewtopic.php?t … ht=refresh should give you a starting point.

Paul

Thanks once again, Paul

Harry - suitably embarassed javascript:emoticon(‘:oops:’)