Error message: Form has been changed since the last time...

[amcg]

Hello - I'm having a bit of a problem, and that's an understatement.

Firstly, I'm working with an Access 97 front end with a SQL Server back end and it's a multi-user system.

I am bring driven up the walls by the following message:

"'[FormName]' has been changed since the last time you opened it, either by another user or because another instance of it was opened on your own machine"

The situation is made more confusing due to the fact that I have actually got two versions of the front end - a Live version and a Test version. The form was tested to death in the Test environment before it was transferred to the Live version and no bugs were found whatsoever (I presume that this is because it was only tested with a maximum of three uesrs at any one time, whereas the Live system can and does have anything up to 20 users working on it simultaneously). As soon as it was made Live however this error message appears any time that a user tries to close the form after he/she has been working on it for a while. I still haven't got a clue as to what is prompting the message as the program does not at any point save the form in any way.

This message has never occurred before for any form and it's causing a lot of problems. I've searched this site for previous posts on the subject and have found three relevant ones, however they do not provide an immediate solution to the problem.

Any help I could get would be most appreciated.

Andy.

 

[AlexMidd]

Are the users only changing data within the form or can they change the design of the form as well? Have fun! )

Alex Middleton

 

[amcg]

No, they're only changing data. Users DEFINITELY do not change the design of the form.

Additionally, I decided to run a multiple user test on the Test environment and it turns out that the problem occurs there too. Therefore it is definitely something to do with the form itself and not with the environment.

Again, any help would be most appreciated.

 

[amcg]

(bump) Again, any help at all would be most appreciated... have tried to implement all sorts of solutions but none seem to work.

 

[AlexMidd]

Well, I have to say I'm stumped. Maybe if you re-post you might get a response from others, as this thread now shows as having several repsonses and is down the list, people tend to overlook it. Have fun! )

Alex Middleton

 

[amcg]

Cheers. Will do.

 

[lunellie]

Did you ever figure out what was causing this error. I am having the same problem and don't know how to fix it.

 

[Hasse]

Lunellie (& IrishAndy, if you didn't find the answer yet, but I hope you did...)

I once had the same problem & soon it got even worse
it appeared to be Access 97 being pretty (pardon me the emoticon) unstable.

you can try and check this out:
Woody's Office Lounge

http://www.wopr.com/cgi-bin/w3t/wwwthreads.pl

Access
"Multi user problems on a unix network"
(post 168264 etc, date: 13 aug '02)

Did this help? Please leave a note to those who'll probably follow after you (...) & feel free to leave also a kind word out there, for those who gave that (to me) most useful advise.

Cheers,
Hasse

ps In my case, I combined a number of advises: split the database, converted the frontend to mde, as an extra measure I advised the users to copy in good client server tradition the mde to their pc. Right now, I haven't had any problems no more. Future will tell if this is temporarily (coincidently, almost no multi user use) of it their suggestions really solved the problem. But it certainly is worth trying...