<>
I had the same problem with Oracle. I've found that I have to be careful when I requery the database after I have committed any UPDATE, DELETE or INSERT. I always use stored procedures, which you would have thought would encapsulate the commit, but it doesn't seem to behave like that. It's almost as if the commit is an asynchronous process. What I had to do was to seperate the save and the requery into two seperate methods. If you're not using sprocs (and you should be) then you're more likelly to hit something like this. You may have to close the cursor and re-open it rather than requery it. I'm afraid I'm not expert on VFP's remote data processing as I always use ADO, so this may not be the best answer.
Hope you sort it out soon.
Pablo
Previous
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
