Access Won't Open

duckster

Registered User.
Local time
Today, 05:26
Joined
Jul 17, 2004
Messages
78
My access database is on one central desktop. When I go to the office, my laptop "connects" with this central desktop and uses the database. Also, my partner's laptop connects with this central desktop as well.

For some reason, when I connect to the central desktop's database via my laptop at the office, my partner can't connect to it. When he doubleclick's the .mdb file, nothing happens, no error message, nothing. Properties don't even come up when right-clicking the icon.

However, when my partner is connected with the central desktop's access database, I can still connect to it.

We both used to be able to connect to the central desktop with no problems.

Not sure what is the problem now. I've tried changing the security levels of the macros on my laptop, as well as the access database, but no luck. Does anybody know what could be causing this?

Thanks for your help. :confused:
 
Last edited:
Does everybody must have full permissions [edit/add/delete] to directory that the db is located in?
 
I do not have any permission requirements or security levels set up right now, so am not sure why my partner cannot open the file whenever I have it opened. The funny thing is, when he has it open though, I can still open it (but it doesn't work when I have it open, and he tries to open it subsequently).
 
Here's a few more details. I just upgraded to Windows Service Pack 2, and now when I access the central desktop's database (via my networked laptop), i get a message:

error.jpg


When I click Ok, it will open as normal. However, when I have it open nobody else on the network can open the database. Also, when my partner opens it first, I cannot open it. By being unable to open it, what I mean is nothing will happen, no hourglass, no error message, nothing.

The Tools--> Options --> Advanced tab does have "shared" checked. Also, there are no restrictions on user permissions.

I believe it may be a Service Pack 2 issue, but am not sure.

Help please.
 
Set your Access macro security settings to LOW.
 
The macro security levels are already set at low at the moment. I think it may be a service pack 2 issue?

At the moment my laptop can access and open the database (located on the central desktop's harddrive), but it will always prompt a message: "Do you want to open this file? Publisher: Unknown Publisher" before it allows me to open.

If my laptop already has access to the database, or when the central database is open on the desktop, my partner cannot even open or access the database (no error message prompt, no "hourglass", nothing). The same goes for my laptop if my partner opens and accesses the central database first...

Not sure what this could be...i've searched numerous threads, changed security and user permission settings to shared, etc. and still no luck.

My database is not "split" in any way right now, and no administrator or users have been created or assigned.

:confused: :confused:
 
I've researched digital signatures, but no luck.

I think it may a service pack 2 issue, b/c my laptop is unable to access the central desktop's database right after i upgraded to service pack 2. Before, I had service pack 1, and the central desktop (where the database is located) had service pack 2. Now, when the central desktop database is open, I cannot access it via my laptop in the network.

Currently, both my laptop, my partner's laptop, and the central desktop (where the main database is located) have the same version of xp pro, and service pack 2, and access 2003.

Anybody know about this issue? Thanks again.
 
Just wanted to give you guys an update, as it works now.

Basically, you actually have to open the general Access Program first, and open the database from the File menu directly (as opposed to just opening the database by double-clicking it).

Weird, but it works now, problem solved. If anyone knows why you must open it from the File menu, please feel free to post...thanks!
 

Users who are viewing this thread

Back
Top Bottom