|
-
Mar 27th, 2006, 09:30 PM
#9
Frenzied Member
Re: Recommended course of action in handling concurrency conflicts
i think there is a problem with the refreshing of records in her UI. maybe after you edited her records, her UI is not refreshed or did not get the latest recordset from your db.
as what i have observed with my previous applications, the recordset is just a temporary storage of data that comes from your database and is being stored in your application. if you dont refresh it or requery it, it wont give you the exact updated result commiing from your database. so i think there should be a requery event in her UI or i suggest it should be in both ways. and to prevent overusage of bandwidth, it is advisable, for my own opinion, to do the refreshing of recordset at 1 minute interval or just wait for the user to click a refresh button.
On error goto Trap
Trap:
in case of emergency, drop the case...
****************************************
If this post has been resolved. Please mark it as "Resolved" by going through the "Thread Tools" above and clicking on the "Mark Thread Resolved " option. if a post is helpful to you, Please Rate it by clicking on the Rate link right below the avatar
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|