MS Developer exentions and MDW question?

[stephen3]

Hi

Im trying to use the developer extensions in Access 2003 to package my database with an installer, now when packaging the database you get the option to include an MDW security file however this then copies the MDW on to the users PC

and refernaces the MDW on the users C drive in the shortcut in creates. How can i get it to referance my MDW file on my server ? so when i need to make changes to group permissons ect these can be made in the MDW on the shared server

Thanks

 

[ghudson]

Do all of the users already have Access 2003 installed?

If so... Then you do not need to use the package and installer. You can simply give the users the files they need [front end of the db, the mdw, and your custom shortcut] to be installed onto their hard drive. I also suggest that you re-think having the users share a mdw file. Each user should have a copy of the front end and the mdw file on their hard drive for those two files should not be shared. You can use WinZip to package the files [I use the WinZip Self-Extractor 2.2] to unpack your files in the location you want. You should have the shortcut file installed in the \All Users\ directory. Your custom shortcut will contain the info to open the correct db and your custom workgroup file.

 

[stephen3]

Hi thanks for that

there using a mixture of 2002/2003 which i presume wont cause any problems

Also i was under the impression that all users need to use the same MDW file otherwise how do i change permissons reset passwords ect with out direct access to the MDW file on the users PC?

what sort of issues can i expect if they all use the same MDW file?

Thanks

 

[ghudson]

Hi thanks for that

1) there using a mixture of 2002/2003 which i presume wont cause any problems

2) Also i was under the impression that all users need to use the same MDW file otherwise how do i change permissons reset passwords ect with out direct access to the MDW file on the users PC?

3) what sort of issues can i expect if they all use the same MDW file?

Thanks

1) I am not sure if Office 10 [Access 2002] will work as nicely as Office 11 [Access 2003]. I know that Office 11 will allow you have a user open an Access 2003 db with the /Runtime switch without actually having to install the Runtime files like Access 97 forces you to.

2) They do. They need their own copy on their hard drive. Just like they need their own copy of the front end on their own hard drive.

3) Locked database

 

[stephen3]

hi

regarding point 2? if they need there own copy of the MDW file on there PC then surely i will have no way of changeing group permissons/passwords and the like?

i was going to provide everyone with there own copy of the front end which connected to a shared MDW on the server which would allow me and other specified users to update group/permisson rights?

thanks

 

[ghudson]

Yes you do [or can]. Just make the changes to your copy [developers] of the front end and your copy [developers] of the mdw file. Then distribute them to the users computers when you have new updates.