General information
Category:
The Mere Mortals Framework
Title:
Using WhereType = 4 (timestamp) in remote views
Environment versions
Network:
Windows 2003 Server
We have a vfp front-end app with sql 2k5 backend that use remote views. For the remote views, we've been using WhereType = 3 so far without major problems. Recently we are researching about using WhereType = 4 (timestamp) mainly for performance reason, among others.
I am currently testing this for a selected tables. Added timestamp in sql table, modified an updatable remote view to include timestamp column in the select clause, WhereType to 4, etc. Ran a data-entry form in the app that update/delete/insert using this remote view, and the form seems to save fine the first time. If I make another change WITHOUT exiting the form, and click save, then I get a 'update conflict' error.
Do I need to requery each time I save to refresh the timestamp field in the view? Is there any other option that I'm missing? I'm trying to avoid an extra requery if I could. Is there a framework method that 'refreshes after an update'?
A solution at the framework level would be nice.
Thanks,
Sid.
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only