Strange startup problem

[Matt Schwartz]

I have a strange situation, and I'm not sure even where to start
troubleshooting. I have a client who has a small network - 6
workstations, one server running Windows 2003 Server Standard edition.
They have an Access 2003 database that sits on this server. They have no
password protection on the access database - everybody has full access to
it.

We setup shortcuts on each persons desktop to the access database using
UNC paths (instead of mapped drives). The first person double clicks on
the shortcut, the database opens up perfectly. Every other person who
double clicks on the shortcut can't get in - nothing happens. They
double click, and double click and double click but access is not
launched and the database is not opened.

This occurs no matter what order they go into the database - the first
person can always get in by double clicking, but nobody else can. This
occurs whether they double click on the shortcut, or if they navigate
through My Network Places and double click directly on the file.

However - they can always access the database by launching Microsoft
Access, then choosing file->open and finding the database. That works
whether they are the first, second or last one in.

Does anybody have any idea why something like this might happen?

Sincerely,
Matt Schwartz
Nelix, Inc.
(e-mail address removed)
www.nelix.com

 

[Bill Mosca, MS Access MVP]

Matt

I won't even start on telling you you should split your database because you
are asking for corruption with any multi-user Access database.

That said...

Change your shortcut to include the Access path as in )all one line):
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE"
\\MyServer\Databases\MyDatabase.mdb

By including the Access path, the db will be opened in shared mode. Doing it
your way will open it in exclusive mode when the first user gets in.

 

[Arvin Meyer [MVP]]

Someone has set the database to open exclusively. You can fix that by going
to Tools >>> Options >>> Advanced and resetting it to Shared. There also may
be a problem with permissions on the database server. Users need every right
except Full Control in order to run the database properly.

Now lets talk about your setup. You have a problem which will eventually
cause the database to corrupt. Split your database into a back-end with all
the tables, and a front-end with everything else. There's a wizard for doing
that: Tools >>> Database Utilities >>> Database Splitter. Now place a copy
of the front-end on each workstation. The users will now share only the
data.

 

[Guest]

Hi Matt,

To add a little to what Bill and Arvin have already mentioned, perhaps you
will find this document useful:

Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html

The second paragraph includes a link to a short article that explains the
benefits of splitting an application.

I advise never including your e-mail address in a newsgroup posting. That's
just begging for some spammer to harvest your address, and start releasing a
torrent of unwanted messages your way.

Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html

 

[Baz]

I can't explain what you are finding, but I can say that it doesn't sound
like a good way to set up a multi-user database. You should split the
database with forms, reports etc. in a front end, and only the tables/data
in a back end. Then, put the back end on your server, and give each user a
local copy of the front end, linked to the back end.

Hence, no-one needs to directly open the back-end file on the server, and
your problem will go away. Plus, you will have a much more robust set-up.

 

[Baz]

Sorry for repeating what others have said, 'tis the OP's fault for
crossposting.

 

[Matt Schwartz]

Thanks everybody for the great suggestions! Sounds like I should split the
data into a separate database, and change the shortcut to include access in
it.

Thanks again for your help! I greatly appreciate it!

Sincerely,
Matt Schwartz