How can I get my Database to Use correct workgroup file

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi Guys,

I read some information earlier concerning creating shortcut as below

"full path to msaccess.exe"
"full path to mdb/mde file"
/wrkgrp "full path to securing mdw file"

I'm a bit stuck as we are working globally and the path to MSACCESS.EXE is
different per PC

syntax I thought to use on properties of shortcut icon are as below:

Target - "\\\weblink\subfolder1\sub2\sub3\sub4\sub5\sub6\sub7\"name of
database.mdw"

Start in: - "\\weblink\subfolder1\sub2\sub3\sub4\sub5\sub6\sub7" /wrkgrp
"\\weblink\subfolder1\sub2\sub3\sub4\sub5\sub6\sub7\workgroupsubfolder"

Also - I get an error when I try add this to the 'start in' line so I'm not
sure I did correctly

Could somebody advise what I'm doing wrong and whether it's possible to do
this with the different MSAccess start up settings on PCs

Thanks for your advice
 
huzzlepuzzle said:
Hi Guys,

I read some information earlier concerning creating shortcut as below

"full path to msaccess.exe"
"full path to mdb/mde file"
/wrkgrp "full path to securing mdw file"

I'm a bit stuck as we are working globally and the path to
MSACCESS.EXE is different per PC
Click to expand...

Then you will have to create a shortcut custom to each PC unless you can find or
create a utility that can figure that out for you. Command line arguments
require that the executable be what you point at with the MDB and MDW being
arguments for the command.

For example, the Access runtime setup program will create a shortcut that
automatically points to the Access executable regardless of where it is located
on the target PC so this must be possible. I assume it pulls the location from
the registry.
 
Hi Rick,

Thanks for this, I'll issue instructions on how to set upthe Shortcut for
individuals then as there shouldn't be too many users
 
If the PCs support scripting, you could probably write a short script
to (1) get the location of msaccess.ese from the registry, then (2)
create the correct shortcut for that PC.

You'd do (1) by looking at the default value of
HKEY_LOCAL_MACHINE\Access.Application\shell\open\command, or somesuch
(I don't have Access here to check), and ignoring the parameters.

HTH,
TC
 
Back
Top