msaccess.exe not located on the same path

[cterrazas]

I have a secured access 97 database in the network and I used a shortcut that includes msaccess path, database path and workgroup path. Everything works fine, but the problem is that for some reason not everybody on the network has MSACCESS.EXE located on the same path.
Is there a diferrent way to get this database started without having to create a shortcut telling where msaccess.exe is? I would think the system would recognize the database file and get it started with the proper application, like it normally does whith any other file.
Thanks in advance for any suggestions.

 

[Vassago]

THe installation directory of Access being different would not cause that error. That error is actually a windows file association error where windows has the database file associated with Access in one path, but Access is actually installed on a different path. To fix this, try reassociating the database extensions with Access on the computers this is happening on.

Try this and let me know what happens.

Vassago

 

[ghudson]

The shortcut allows you to open the db without having to "join" a computer to a workgroup. Joining a computer to a workgroup creates the unnecessary burden on the user to log into the workgroup just to open any Access db (new or old).

The secured shortcut specifies where everything is located (msaccess.exe, workgroup, MDB, user)
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /wrkgrp "X:\Testing\YourWorkgroupFile.mdw" "X:\Testing\YourDatabase.mdb.mdb" /user TestUser

Access should be located in the default directory if everybody is using the same version of Access and they only have one version of Office installed on their computer.
C:\Program Files\Microsoft Office\Office

You might see if your MIS folks can reinstall Office in the default directory for that will ease your task.

A shortcut can not determine where the MSACCESS.EXE file (Acces installation directory) is located but you can do that with in VBA.

SysCmd(acSysCmdAccessDir) & "MSACCESS.EXE"

Test it with...
MsgBox SysCmd(acSysCmdAccessDir) & "MSACCESS.EXE"

HTH

 

[George Bush]

I didn't think about that... I didn't realize it was a shortcut. Can't a shortcut search for Msaccess.exe if it can't find it in the directory specified anyway?

 

[cterrazas]

THe installation directory of Access being different would not cause that error. That error is actually a windows file association error where windows has the database file associated with Access in one path, but Access is actually installed on a different path. To fix this, try reassociating the database extensions with Access on the computers this is happening on.

Try this and let me know what happens.

Vassago

Changing all computers will be a lot of work and probably the client won't buy into that. This database will be used over the network starting 4 different sites and in the future to up to 10. I could not tell how many user will be involved with the DB They already have a secured database working fine, but there is no one that could tell me how this was set up. But thanks for all the suggestions.