A shared database file won't open when double-clicked.

[evander]

Hi everyone. I do hope to get answers here.

PROBLEM: A shared database file won't open when double-clicked.

Here are the details:

(1) The database file is shared among five (5) users or computers.
(2) All the five (5) users can open the database file by double-clicking it, well only one user at a time.
(3) When User 1 opens the database file by double-clicking it (thus it is now open) and User 2 tries to open the same shared database file by double-clicking it, nothing happens in the computer of User 2.
(4) However, User 2 can open that shared database file by opening Microsoft Access first.
(5) The shared database file is made in Microsoft Access 2003.
(6) The shared folder where the database file resides is open to all users. They can cut, copy, paste, delete, edit etc...
(7) All users are using Windows XP Service Pack 2.
(8) The router is a Linksys WRT54N.
(9) All users are connected to the router via LAN UTP cable.
(10) Some users have their firewalls turned on. Others turned off.


(11) The database file was made in a development PC that's running in Windows 7 Ultimate.
(12) All users have their copies of Microsoft Access 2003 set to "Shared," which is the option found in Tools > Options > Advanced.
(13) File association is correctly set up.
(14) No error message is generated.
(15) The database file does not implement User-Level security (yet).
(16) The database file does not have a database password.
(17) The database file has been subject to conditions that can corrupt it, but I haven't encountered any message telling it's corrupt... Sudden shutdown of PC, hibernating, Access was forcefully shut down by clicking the "End Now" button.
(18) No database object was ever corrupted: tables, queries, forms, reports, modules, pages.
(19) The database's VBA uses DAO in some areas.
(20) No object-oriented programming.

Thank you so much guys. Please excuse me when I commit mistakes in English because I'm not a native speaker. By the way, I'm not an IT professional.

-evander-

[Datagopherdan]

Are the users all using the same file? If so, try splitting it into a front and back-end, which is the preferred way. Each user would have their own front-end that would be linked to the same back-end file where your data is.

[evander]

Datagopherdan: Will I be able to implement User-Level Security if it's split? I need ULS for the time being, before I migrate the data to PostgreSQL, with Access still acting as a front-end.

[evander]

Datagopherdan: Yes they are using the same file. It's not split. And they open the database file itself. No shortcut icons involved.

[Datagopherdan]

Yes, it will still be secure. Here's a link for instructions on splitting the database. http://databases.about.com/od/tutorials/ss/splitaccessdb.htm

I didn't go through the entire article but what you want to do is have the users place their copies of the front-end on their local machines and then your back-end file would be in a shared network drive. You can't have users opening up the same Access file like that. You're going to run into all kinds of issues, that's why each user needs their own copy of the database that will be linked to the same back-end file that contains your data.

[evander]

Datagopherdan: I can handle the splitting. But I don't know how to implement ULS in an already-split database. I guess I'd split the DB for the meantime without any security since I'm in the testing phase.

[Datagopherdan]

I thought you said that it wasn't split that they are using the same file. If you already have ULS on it, all you would have to do is split it.