Where to save front-end

[AndrewAfresh]

I’m developing a split back-end/front-end application. What do people consider the best place to store the front-end?

[pbaldy]

On each user's PC. If you mean where on the PC, I don't know that it really matters. I used to use specific directory:

C:\AccessApps

After experiences with Terminal Server/Citrix and the need for each user to have their own copy in that environment, I now use:

C:\AccessApps\UserName

and let my version control utility examine the user name and drop the front end into that folder.

[AndrewAfresh]

Would anyone have problems if I copy it to c:\documents and settings\username\application data?

[aladrach]

Not at all. That's where I have mine installed. Works very well. Also gets around the "Trusted Locations" problem sometimes.

[pbaldy]

I don't foresee any problems with that.

[Mclaren]

and let my version control utility examine the user name and drop the front end into that folder.

Would you be willing to share your "Version Control" utility ?

[pbaldy]

It's written in VB6 and customized for our environment, so not really made to be used by anyone else. I use Environ("UserName") to get the logged in user, Dir() to see if the folder for that person exists, and MkDir to create the folder if it doesn't.

[phi11yguy19]

If you have an install routine, ideally you present the users with a form that has the default path of your preference and a "..." button to open a Browse for Folder dialog to pick somewhere else as they desire.

[Rod]

Have you considered saving the directory path in the registry? I believe SaveSetting, etc. uses the current user hive so everyone may have a different path.

[Rod]

Forget my comment about SaveSetting - this has to be done outside the Access front-end! I wasn't thinking. Registry option is still valid though.

[Mclaren]

I have found out that the company i am working for is upgrading to office 2010 and win 7 before the years end, so i have to start re-writting and testing using access 2010. i know 2010 uses trusted locations.

I want someway of making the following happen :

initial setup.

User clicks hyperlink sent via email
hyper link actions some kind of scrit that :
1. Copies front end and all front end files eg images folder etc to users pc under C:\DB\
2. places 2 shortcuts on the users desktop, 1 to the frontend and one to the vb script for future updates.
3. have the location of the front end added to the trusted locations automatilcally.

Future updates:
1. the user clicks the shortcut on the desktop created when the initial setup was done.
2. updates are made to the db loction folder in the c: directory as shown above.

if i use the same location on all PCs surely this will minimise the coding required when allowing users to select their own locations, as an example, i can ensure that my links to the images that are not embedded are all in the same location and can be hard coded, other wise if the user moves the location of the frontend, images may give error messages when not found.

I am not a script user and have found a rough example of what i want to happen, but i cannot get all the things to work as i do not fully understand what the code is doing or means.

[pbaldy]

Since you haven't posted any code for us to fix, I assume you're looking for someone to do it for you? There's a batch file method here:

Bill has a batch file method here plus links to Tony's FE Updater:

http://thatlldoit.com/howtosarticles.aspx#fe_updater

[Mclaren]

Since you haven't posted any code for us to fix, I assume you're looking for someone to do it for you? There's a batch file method here:

Bill has a batch file method here plus links to Tony's FE Updater:

http://thatlldoit.com/howtosarticles.aspx#fe_updater

At this point in time, no, i need to concentrate on getting the DB converted from 2003 to 2010 and working correctly. it is not a complicated DB so it shouldn't take too long.

I would actually just need some help with it. When i am ready i think i will post what i need to.

Right now, busy learning the new changes i need to know for access 2010.