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

Multiple instances of frontend - problems?

P: n/a
If a user happens to open multiple instances of her frontend, what kind of
problems can occur?

For example, one user reported that she was able to, once or twice, bypass
the evaluation procedures that check a new record before it's allowed into
the database. She said that this happened on a day when her computer
behaved strangely in general. We have not been able to repeat/reconstruct
the error, and I wonder if the explanation can be that she had multiple
frontend instances open on the same machine on this occasion.

TIA
Johan
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I've never seen anyone bypass the validation routines or rules by opening
multiple instances of the same mdb front end.

The most common issue is if one of the instances is placed in design view
while the other is in use, or one tries to save the object (e.g. DoCmd.Close
acForm "Form1", acSaveYes) while the other is open, the object save (not the
record save) will fail. Using an MDE instead of an MDB might avoid that.

Other than that, you would expect only the normal locking errors.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Johan" <no*****@nospam.com> wrote in message
news:Xn**********************@130.133.1.4...
If a user happens to open multiple instances of her frontend, what kind of
problems can occur?

For example, one user reported that she was able to, once or twice, bypass
the evaluation procedures that check a new record before it's allowed into
the database. She said that this happened on a day when her computer
behaved strangely in general. We have not been able to repeat/reconstruct
the error, and I wonder if the explanation can be that she had multiple
frontend instances open on the same machine on this occasion.

TIA
Johan

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.