Locked Forms - Access03

[DanG]

My company just upgraded from A97 to A03 (Multi User). In A97 there were only rare instances when I could not change forms in design view while other users were in the same database, now it seems in A03 I am not able to change anything, anytime on a form (and other objects I am sure) except when all users are out of the database.
Has A03 changed this drastically? It seem that if it has it has only made life harder for us (b**ch Moan, b**ch Moan)
Just checking to see if I'm missing something here.

Thanks

 

[RuralGuy]

Is your db split to FrontEnd and BackEnd? If not then read this link: http://allenbrowne.com/ser-01.html

 

[ghudson]

You can not save design changes unless you are the only one in the db. You should not be making changes to a live db if other users are in it. That is a disaster waiting to happen. Search around for there are code samples showing you how to kick everybody out so that you can make and save a design change. You should "exclusively" open the db to ensure nobody sneaks in while you are making a change.

But as mentioned before, you really should split your db and distribute the new version when needed. Everybody should have their own copy of the front end installed onto their hard drive and each front end must be linked to the one back end on the server.

 

[DanG]

Thank you for the response.
I have not split my database primarly because it is on Citrix (a thin client) so I didn't see how I could benifit from splitting.
So, has A03 changed so much it won't even let you make changes unless you are in it exclusively? (putting aside the issue of if I should or not of course).
I have a good system for kicking users off if needed, but do not like to over use that option if you know what I mean.

 

[ghudson]

I have not split my database primarly because it is on Citrix (a thin client) so I didn't see how I could benifit from splitting.

Wrong!

So, has Access 2003 changed so much it won't even let you make changes unless you are in it exclusively? (putting aside the issue of if I should or not of course).

It has been that way since Access 2000.

 

[ghudson]

Just to clarify... There are many reasons for splitting a db. Search the forum and discover the benefits and reasons you should split your db. I have deployed one application on a Citrix environment and I treated it the same way as a NT server... I split the db.

But that is my opinion and you get what you pay for when asking for advice in a public forum.

You should have posted back if you had any more [specific] questions in regards to splitting a db. Since the subject has been asked and answered in so many threads I am quick to suggest that the inquisitive use the resources within this forum and learn from thier previous experiences.