> Having created a secured database and now have all the relevant
> passwords etc, it created a shortcut which i now run from.
> However, I need to distribute this file on to a shared drive and i
> cannot find the main file and can only run off the shortcut.
> ANy ideas?

"Joan Wild" wrote:

> Right-click the shortcut and check the line in the target box.  It'll have
> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"
>
> Just copy the mdb and the mdw from the paths indicated to the shared drive.
>
> You'll need to modify your shortcut, changing the paths to reflect the new
> location of the files.  Then you'll need to provide your users with a
> similar shortcut (it may differ slightly if users have a different path to
> msaccess.exe than you do).
>
> Having said that, you should consider splitting the mdb.  Put just the
> backend on the server, and give each user a copy of the frontend on their
> computer.  The shortcut would then be changed to
> "path to msaccess.exe" "path to frontend on local machine" /wrkgrp "path to
> secure mdw on server"
>
> If you split the secure mdb, don't use the splitter wizard.  See
> www.jmwild.com/splitsecure.htm
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Matt Dawson wrote:
> > Having created a secured database and now have all the relevant
> > passwords etc, it created a shortcut which i now run from.
> > However, I need to distribute this file on to a shared drive and i
> > cannot find the main file and can only run off the shortcut.
> > ANy ideas?
>
>
>

> Joan,
> Thank you. However, i have already split the database using the
> wizard. Will this make a difference?
> Matt
>
> "Joan Wild" wrote:
>
>> Right-click the shortcut and check the line in the target box.
>> It'll have "path to msaccess.exe" "path to mdb" /wrkgrp "path to
>> secure.mdw"
>>
>> Just copy the mdb and the mdw from the paths indicated to the shared
>> drive.
>>
>> You'll need to modify your shortcut, changing the paths to reflect
>> the new location of the files.  Then you'll need to provide your
>> users with a similar shortcut (it may differ slightly if users have
>> a different path to msaccess.exe than you do).
>>
>> Having said that, you should consider splitting the mdb.  Put just
>> the backend on the server, and give each user a copy of the frontend
>> on their computer.  The shortcut would then be changed to
>> "path to msaccess.exe" "path to frontend on local machine" /wrkgrp
>> "path to secure mdw on server"
>>
>> If you split the secure mdb, don't use the splitter wizard.  See
>> www.jmwild.com/splitsecure.htm
>>
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> Matt Dawson wrote:
>>> Having created a secured database and now have all the relevant
>>> passwords etc, it created a shortcut which i now run from.
>>> However, I need to distribute this file on to a shared drive and i
>>> cannot find the main file and can only run off the shortcut.
>>> ANy ideas?

"Joan Wild" wrote:

> Right-click the shortcut and check the line in the target box.  It'll have
> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"
>
> Just copy the mdb and the mdw from the paths indicated to the shared drive.
>
> You'll need to modify your shortcut, changing the paths to reflect the new
> location of the files.  Then you'll need to provide your users with a
> similar shortcut (it may differ slightly if users have a different path to
> msaccess.exe than you do).
>
> Having said that, you should consider splitting the mdb.  Put just the
> backend on the server, and give each user a copy of the frontend on their
> computer.  The shortcut would then be changed to
> "path to msaccess.exe" "path to frontend on local machine" /wrkgrp "path to
> secure mdw on server"
>
> If you split the secure mdb, don't use the splitter wizard.  See
> www.jmwild.com/splitsecure.htm
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Matt Dawson wrote:
> > Having created a secured database and now have all the relevant
> > passwords etc, it created a shortcut which i now run from.
> > However, I need to distribute this file on to a shared drive and i
> > cannot find the main file and can only run off the shortcut.
> > ANy ideas?
>
>
>

> I also have a problem, in that I split the database and was then told
> i had to add more tables and didnt then do it in the backend! so I
> have two backend tables
> Is this a problem?
>
> "Joan Wild" wrote:
>
>> Right-click the shortcut and check the line in the target box.
>> It'll have "path to msaccess.exe" "path to mdb" /wrkgrp "path to
>> secure.mdw"
>>
>> Just copy the mdb and the mdw from the paths indicated to the shared
>> drive.
>>
>> You'll need to modify your shortcut, changing the paths to reflect
>> the new location of the files.  Then you'll need to provide your
>> users with a similar shortcut (it may differ slightly if users have
>> a different path to msaccess.exe than you do).
>>
>> Having said that, you should consider splitting the mdb.  Put just
>> the backend on the server, and give each user a copy of the frontend
>> on their computer.  The shortcut would then be changed to
>> "path to msaccess.exe" "path to frontend on local machine" /wrkgrp
>> "path to secure mdw on server"
>>
>> If you split the secure mdb, don't use the splitter wizard.  See
>> www.jmwild.com/splitsecure.htm
>>
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> Matt Dawson wrote:
>>> Having created a secured database and now have all the relevant
>>> passwords etc, it created a shortcut which i now run from.
>>> However, I need to distribute this file on to a shared drive and i
>>> cannot find the main file and can only run off the shortcut.
>>> ANy ideas?