Shortcut prevents second user from opening database

[Guest]

When multiple access users try to access database from different systems
through a shortcut the system does nothing. When second user enters through
Access they can enter the database with no problem... The database allows
multiple users to access but the shortcut only works for the first user that
enters. All others have to enter through Access. What prevents the second
user access through the shortcut from another machine?

 

[John W. Vinson]

On Tue, 7 Aug 2007 19:30:43 -0700, BJH Data <BJH

When multiple access users try to access database from different systems
through a shortcut the system does nothing. When second user enters through
Access they can enter the database with no problem... The database allows
multiple users to access but the shortcut only works for the first user that
enters. All others have to enter through Access. What prevents the second
user access through the shortcut from another machine?

What's the target line on the shortcut? View its Properties and copy and paste
the command line here...


John W. Vinson [MVP]

 

[banem2]

On Tue, 7 Aug 2007 19:30:43 -0700, BJH Data <BJH


What's the target line on the shortcut? View its Properties and copy and paste
the command line here...


John W. Vinson [MVP]

However, sharing same database between users might not be a good idea.
Instead split database to backend and frontend using Database Splitter
Wizard and copy frontend on each workstation.

Regards,
Branislav Mihaljev

 

[Guest]

i have same problem

i found that some of the systems were working. the difference was the
following:

Registry setting:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Access\Jet\4.0\Engines]
"SystemDB"="C:\\PROGRA~1\\COMMON~1\\System\\SYSTEM.MDW"

and the file C:\PROGRA~1\COMMON~1\System\SYSTEM.MDW was on on all the
systems that worked.

so i put it eveywere.

Now the only problem is the mapped drives that goto dfs entries still do not
work. Found that changing the mapping to old unc names fixed that problem.

It worked for me.