Re: Using Microsoft Access as a Front-end to MySQL
I haven't had a lot of problems when the application side has just been updating the data through the forms. You can get warnings/errors when the same row has been updated by more than one user; but Access seems to be constantly updating its live record sets all the time.
Problems can happen if Alice is already working with record 365, and the Bob updates it, and then Alice tries to update it with her changes. As I recall, Alice will get a cryptic error message. It would be easier for the users if you trap these errors and at least give them a friendlier error message.
I've had more problems when I was editing records in the VB code through RecordSets, especially when combined with editing the same data on forms. That's not necessarily a multi user problem; however, you have almost the same situation because you have one user with multiple connections to the same data.
Love Is Life
Subject
Views
Written By
Posted
71967
February 14, 2007 01:10PM
18804
July 08, 2007 05:10PM
14551
August 24, 2007 05:57AM
11316
February 06, 2008 01:16PM
7393
September 01, 2009 11:03AM
Re: Using Microsoft Access as a Front-end to MySQL
7623
March 02, 2009 06:09AM
8350
December 01, 2008 01:49PM
6126
May 15, 2009 08:45AM
6339
May 25, 2009 05:12PM
6192
May 26, 2009 11:33AM
6511
April 03, 2009 02:44AM
5868
May 01, 2009 08:36PM
5987
May 02, 2009 04:37AM
6204
June 08, 2009 10:28AM
7724
June 09, 2009 04:02PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.