After MDW setup in local, how can I move it to company's intranet?

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

Guest

I develop the ACCESS and use anothername.mdw (as suggested) to save my all
security settings in local computer. How come this security will effect all
my mdbs?

Can different mdbs use different MDW???

After testing, I will move it to company Intranet drive. Should the MDW
move too? If so, how can I do it???

Thank you!!!
 
Yes, different MDBs can use differen MDWs. To ensure that you've associated
the correct ones together, use a short-cut to open the database:

<full path to msaccess.exe> <full path to mdb file> /wrkgrp <full path to
mdw file>

The MDW should move with the MDB: all users will require Read, Write,
eXecute and Delete access to the folder(s) where the MDB and MDB files
exist.

Hopefully you've split your application into a front-end (containing the
queries, forms, reports, macros and modules), linked to a back-end
(containing the tables and relations). Only the back-end should be on the
server: each user should have his/her own copy of the front-end, preferably
on their hard drive.
 
Dear Douglas:

Thank you very much for the methods you provide. It really help.

1. After all the security is set, can you provide the better way how to move
everything (mdb and mdw) to the designated server drive?
2. I never think about seperated front-end and back-end, is there have
optimized way to do it? (looks like complicated) That means after this
program is launched, should I do the work like "automatic" installed of those
"front-end" stuffs to user's drive???
 
Dear Doug:

Thank you for your advice, it is not too late. Also if I seperate the
front-end and back-end, I will like make it a exe file. What is the
procedure I should do? Spilt first, and then make exe?
Also if involving the MDW, should I include this one when I make exe???

Thanks.

Vivi
 
Back
Top