Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Question on .mdw security with .mde front-end DB's

Status
Not open for further replies.

Melagan

MIS
Nov 24, 2004
443
US
Greetings,

I have recently split my DB. Currently, the front-end, back-end, and workgroup files are all on a shared network folder. All of the users are pointed to a single front-end via a shortcut that has the /wrkgrp command switch. This works fine, but I am wanting to make .mde and distribute to each user instead of using a shared .mdb front-end.

Is there any way to tell the .mde file to use the correct .mdw file without using a command switch or manually joining the computer to the workgroup file?

Ultimately, I'd like for each computer to stay connected to the default workgroup file; Each user should have the .mde front-end on their desktops and upon launching, that .mde file should already know the correct workgroup file to use to connect to the back-end. I'd like to avoid having to use a shortcut to launch the .mde if at all possible.

Hopefully that makes sense; thanks in advance for any help you can provide!


~Melagan
______
"It's never too late to become what you might have been.
 
Hi,

Yes you can by using a shortcut to a batch file ion the server instead. The instructions in the batch file check the version of the front end against the version on the local c drive. if not the same it will copy it to c. at the and it will start the front end with the right mdw:
Code:
echo off

if not exist "C:\DATA\FCM\" mkdir "C:\Data\FCM\"
cd "C:\Data\FCM\"


rem copy database to C if there is a newer version
if not exist "C:\Data\FCM\versionfile1A.txt"  copy "N:\pathetothenetweorkfile\Mydatabase.mde" "C:\Data\FCM\Mydatabase.mde"
					   
rem copy versionfile if necessary
if not exist "C:\Data\FCM\versionfile1A.txt"  copy "N:\pathetothenetweorkfile\versionfile1A.txt" "C:\Data\FCM\versionfile1A.txt"

rem copy database to C if it doesnt exist at all
if not exist "C:\Data\FCM\versionfile1A.txt"  copy "N:\pathetothenetweorkfile\Mydatabase.mde" "C:\Data\FCM\Mydatabase.mde"

rem start database
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\Data\FCM\Mydatabase.mde" /WRKGRP N:\pathetothenetweorkfile\MySystemdatabase.mdw"


exit

the versionfile is just a empty textfile, i only use it to change the name (ie 1A becomes 1B if a publsih a new mde). When publishing a new mde you change two things: the versionname and the same name in batchfile.
EasyIT
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top