By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,827 Members | 2,256 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,827 IT Pros & Developers. It's quick & easy.

Split Multi-User DB but still getting data change errors

P: 2
I'm using MS Access 2003 1 form with 7 sub forms, updating 7 tables. I've split my database but still getting data changes error messages when multiple people are in the database. Any help would be greatly appreciated.

Thanks.
Sep 20 '07 #1
Share this Question
Share on Google+
4 Replies


FishVal
Expert 2.5K+
P: 2,653
I'm using MS Access 2003 1 form with 7 sub forms, updating 7 tables. I've split my database but still getting data changes error messages when multiple people are in the database. Any help would be greatly appreciated.

Thanks.
Hi, dfent.

DB splitting will not prevent attempt of multiple users to edit the same record. Access honestly warns a user that another user has changed and saved the record he tries to save.
You can trap this by handling Form_Error event, which allows you to perform some action, warn a user the way you like or just ignore the situation.

example

Expand|Select|Wrap|Line Numbers
  1. Private Sub Form_Error(DataErr As Integer, Response As Integer)
  2.     Const conRecordSaveConflict = 7787
  3.     If DataErr = 7787 Then Response = acDataErrContinue
  4. End Sub
  5.  
This code just suppress Access warnings silently allowing a second user to save his record.

Hope this makes a sense.
Sep 20 '07 #2

FishVal
Expert 2.5K+
P: 2,653
/* post duplicate */
Sep 20 '07 #3

P: 2
That suppresses the errors but if user 1 is in the database and then user 2 enters and user 1 has the date field selected, when user 2 changes - the changes are seen on for user 1 as well.

Thanks.
Sep 21 '07 #4

FishVal
Expert 2.5K+
P: 2,653
That suppresses the errors but if user 1 is in the database and then user 2 enters and user 1 has the date field selected, when user 2 changes - the changes are seen on for user 1 as well.

Thanks.
Well, and how do you want this conflict to be resolved?
Particular solution depends on user interface implemented in you frontend.
I guess you probably want to lock record when user 1 starts to modify it so that user 2 will see it as locked/read-only.
Am I right?
Sep 21 '07 #5

Post your reply

Sign in to post your reply or Sign up for a free account.