Access Path too long for Target Shortcut (1 Viewer)

[dmeid]

I am trying to apply security to a FE and a BE Datase, by using a short cut that looks somewhat like this.

"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "X:\YourWorkgroupFile.mdw" "X:\YourFrontendDB.mdb"
"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "X:\YourWorkgroupFile.mdw" "X:\YourBackendDB.mdb"

My problem is that the path to apply a workgroup to both FE and BE is too long for the Target field in the Shortcut. It only allows a certain number of characters.

How can I get my full paths applied to this Target: field of the shortcut

All Help is greatly appreciated !!!

 

[ReAn]

Make a batch file (*.bat) with this exact contents:

@echo off
C:\Program Files\Microsoft Office\Office\msaccess.exe /wrkgrp "X:\YourWorkgroupFile.mdw" "X:\YourFrontendDB.mdb" 
C:\Program Files\Microsoft Office\Office\msaccess.exe /wrkgrp "X:\YourWorkgroupFile.mdw" "X:\YourBackendDB.mdb"

Make Shortcut to the Batch File

 

[dmeid]

Thank you soo, much it worked wonderfully!

 

[ReAn]

np, enjoy

 

[rutica]

I know this is an old post, but...

I am trying to do the same thing. Using my batch file works fine, but the DOS window stays open until Access closes.

Here is my .bat file:
@echo off
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "\\nct3\Common\ManagementCenters\ProjectHealth\PADA\Test Databases\securityTest.mdb" /WRKGRP "\\nct3\Common\ManagementCenters\ProjectHealth\PADA\Test Databases\Security.mdw"

I have tried typing EXIT or CLS at the end of the batch file above, but no luck.

How can I get the DOS window to go away after Access opens?

Thanks,

 

[SOS]

Try renaming your .bat file to .cmd instead.

 

[rutica]

thanks for writing. I renamed the file from:

shortcut Test.bat

to:

Copy of shortcut Test.cmd

but it doesn't fix the problem. The Command window still stays open.

I have Windows XP and Office 2003.

Thanks,

 

[SOS]

Try substituting this in your batch file:

"START /I " "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /WRKGRP "\\nct3\Common\ManagementCenters\ProjectHealth\PADA \Test Databases\Security.mdw" "\\nct3\Common\ManagementCenters\ProjectHealth\PADA \Test Databases\securityTest.mdb"

 

[rutica]

Thanks for writing.

It didn't work. Now the DOS windows opens for a second, then closes and Access doesn't open at all.

 

[rutica]

I found the answer! I have to add this line to the beginning:

Start " "

Here is my .bat file:
@echo off
Start " " "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "\\nct3\Common\ManagementCenters\ProjectHealth\PADA\Test Databases\securityTest.mdb" /WRKGRP "\\nct3\Common\ManagementCenters\ProjectHealth\PADA\Test Databases\Security.mdw"


Thanks anway!

 

[SOS]

I did have part of it backwards:

Should be:

"START /I " "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "\\nct3\Common\ManagementCenters\ProjectHealth\PADA \Test Databases\securityTest.mdb" /WRKGRP "\\nct3\Common\ManagementCenters\ProjectHealth\PADA \Test Databases\Security.mdw"

It's been so long since I ran secured databases so hopefully this will work for you (remember to remove any extra spaces from the stuff here as the forum software adds spaces intermittently to the text.

 

[SOS]

Thanks anway!

So you are up and running? If so, great!

 

[rutica]

Yes, it works with the Start " "

Thanks, for your help though!

 

[SOS]

Yes, it works with the Start " "

Thanks, for your help though!

Good, I used the Start /I in some code I had a long time ago and I had found it so at least you figured out how to use it to make it work for you. Glad you were able to get on the path and play with it and get it to work.

 

[marco123]

I used pathTooLongFix, good one

 

[Simon_MT]

I have understood that the path of the database should be short and whilst I had some control over the server configuration mapping of Network drives the BE was S:\Data.mdb. The Fe was C:\Databases\Network.mde. I realise that Access has moved on but old habits (Access 1997) have proved unproblematical.

Simon

 

[Gerald_Brickson]

Exactly, I came to face this issue also. Then someone recommended me Long Path Tool software and I am grateful to that person

 

[The_Doc_Man]

Not that you would necessarily need it because you already have a solution, but if you really wanted to shorten your typing for a long path, there would have been the possibility of using the SUBST command issued at the command prompt.

SUBST drive1:   drive2:/part/of/long/path/string

And you could delete the new virtual drive with

SUBST drive1: /D