Front End Distribution

[thart21]

I have read every post here on "distribution" and "deploying" the front end to the users but can't seem to get how to do it. I see many posts regarding updating the front end and using the runtime version to distribute but can't seem to understand how to initially get the database out to my users.

I have a split db and need to distribute it to about 20+ people. The back end will reside on a shared drive that is mapped the same on everyone's machine.
I also have the FE on the same drive and am currently using a batch file run from a link on our website to open it, therefore we are all using the same front end which is what I am trying to eliminate.

Can I just zip up my FE and email it to my users? Will that maintain the links to the back end when they unzip it to their desktop?

Also, I would like to get some feedback on some software I am thinking of buying for pushing out my updated databases in the future. It is called Access Frontend Loader
http://www.frontend-loader.com/

Has anyone used this before? Would appreciate any thoughts on it or any other program you may have used in the past.

Thanks

 

[ghudson]

I use the WinZip Self-Extractor 2.2 to distribute my files. The free version that comes with WinZip does not allow you to "lock" the location that the files are extracted to. The Self-Extractor 2.2 is an add-on that you can purchase from WinZip.

Yes, your table links will still point to the same location when the user extracts your files. Just ensure you use the UNC address, not a fixed drive address when linking your tables.

 

[thart21]

Thanks for the advice on WinZip and the UNC. I have the full version of WinZip version 9.0 and use it to make .exe files, but can't email them through Outlook so I will just mail the .zip file.

 

[thart21]

Distribut FE

Finally getting back to this.

I created a .exe file from my front end, set it to extract to C:\Training Records on everyone's system, and placed the .exe on my website for everyone to download it from.

I think this is the right way to do this but would appreciate it if anyone sees any future problems I might encounter with this method.

The links to the BE seem to be staying in tact, but, if the user moves the front end to another place on their system, should I expect any problems with the links?

Thanks,

Toni