Write Conflict potentially from a slow server?

[BallunarCrew]

I have a large, Access 2007 database that has one main form with several sub-forms and tabs. I know it takes up a lot of memory. The users are experiencing more and more often the error that tells them the record has been updated by another user, drop changes, copy to clipboard? etc. I have seen this happen when I know there is only one user in the database. This database complexity has grown over time but the core design is the same as it has always been and this issue is fairly recent and becoming more often. Has anyone seen this happen when using an old, slow server? We are waiting on a new one and I don't want to promise the users this will fix the issue if it won't.
Thanks,
Karen

 

[dhookom]

I have seen this occur when you open a new form that shares one or more tables in the record source. You often have to save the record on the first form prior to opening the new form.

Duane
Hook'D on Access
MS Access MVP

 

[BallunarCrew]

Thanks Duane. This main form does has several tabs and sub-forms. Some tabs have sub-forms and some have fields from the main form. I think I am going to try forcing a save each time they leave a tab - maybe a tab.lost_focus event - not sure on the exact coding for that yet. Since it is one main form with tabs, I don't think Access actually opens the sub-forms as the tab is called up but rather opens them all when the main form is opened.

 

[missinglinq]

Just to be clear, we are talking about a properly Split db here, correct? A copy of the Front End on each user's PC and the Back End with Tables on the server?

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[BallunarCrew]

Unfortunately, no, it is not split. I tried that and it made it take 2-3 minutes to open and move from record to record on the main form. Once we get the new server in and setup, I do plan to try that again. This database, in general, needs a total overhaul but there has not been time or budget for that.

 

[missinglinq]

Every symptom you've given can be the direct result of running this as a non-split app. I'm afraid until you get your server situation resolved and the db split you're going to be constantly plagued by these gremlins.

The really weird thing about this is that I've read reports of non-split, multi-user Access databases running fine for extended periods, one as long as 14 years, and then SPLAT! And once they start acting up it becomes chronic until the split is done.

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[TheAceMan1]

BallunarCrew . . .

Until you get the new server, checkout the following reference

Splitting a database is not just for multi-user databases.

See Ya! . . . . . .

Be sure to see faq219-2884 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]