Access 2003

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sameer - 18 Nov 2003 21:31 GMT

Hello everyone,
We are working on a backend sql server database, to which
we are having front end access forms for data entry.
The problem we are facing is that when one developer has a
form open in design view, nobody else can get on the
database and it gives the error: "The database has been
placed in a state by user 'username' on
machine 'machinename' that prevents it from being opened
or locked.
I tried to do some research on it, and saw that Microsoft
fixed this same bug in access 2000 when they released
service pack 1. However, I guess they havent fixed it on
access 2003 yet.
Anybody has any ideas on this problem?
Any help will be really appreciated.
Thanks
Sameer

Reply to this Message

Paul Overway - 19 Nov 2003 00:51 GMT

Not sure where you got the idea this was fixed in 2000 SP1. AFAIK, this has
always been a problem with Jet 4.0 databases. If you want to do multi-user
development, you need to use SourceSafe or merge your changes manually.

--
Paul Overway
Logico Solutions, LLC
www.logico-solutions.com

> Hello everyone,
> We are working on a backend sql server database, to which
[quoted text clipped - 13 lines]
> Thanks
> Sameer

Reply to this Message

Scott McDaniel - 19 Nov 2003 01:06 GMT

This isn't a "bug", it's designed into the system. From what I understand,
all objects are now saved as one big object (I believe it's called a BLOB,
but could be wrong), so only one person can make design changes at a time.
As Paul suggested, you can always use a source control product designed to
handle Access. VSS comes with Access Developer XP (not sure about Developer
2000), it works pretty well.

> Hello everyone,
> We are working on a backend sql server database, to which
[quoted text clipped - 13 lines]
> Thanks
> Sameer

Reply to this Message