G
Guest
Hi,
We run a 3rd party application here built on Access XP. The same mde file
will run under Access 2003, with one problem. It's a secured multiuser app,
so there is a system.mdw file on a Novell file server. We are an organistion
with a number of sites, and each site has it's own Novell server, with it's
own system.mdw file.
Here's the problem. On some of the servers, once an Access 2003 client has
logged in to the system.mdw file, no Access XP clients can log in. The error
message is "Microsoft Access couldn't find file '.....\system.mdw'. This file
is required for startup." The thing of it is that the file is there. Any
other application can open the file (eg, LDBView. Also, the system.mdw file
can be opened in Visual Basic with DAO, or a straight FileOpen call). As long
as another application keeps the file open, Access XP is happy and will log
in ok.
Has anybody ever seen this, or have a clue about resolving it?
Cheers, Elson
We run a 3rd party application here built on Access XP. The same mde file
will run under Access 2003, with one problem. It's a secured multiuser app,
so there is a system.mdw file on a Novell file server. We are an organistion
with a number of sites, and each site has it's own Novell server, with it's
own system.mdw file.
Here's the problem. On some of the servers, once an Access 2003 client has
logged in to the system.mdw file, no Access XP clients can log in. The error
message is "Microsoft Access couldn't find file '.....\system.mdw'. This file
is required for startup." The thing of it is that the file is there. Any
other application can open the file (eg, LDBView. Also, the system.mdw file
can be opened in Visual Basic with DAO, or a straight FileOpen call). As long
as another application keeps the file open, Access XP is happy and will log
in ok.
Has anybody ever seen this, or have a clue about resolving it?
Cheers, Elson