DB file locations when deploying

[Jay]

Is there a "Best Practice" for file location(s) when deploying Access 2007
applications?

For example, what about a split database application on one PC. Where
should the "Front End" (forms, code, etc) file go, and where should the "Back
End" (tables) file go? Is it different for Vista than for XP (ignoring other
Windows versions for now)?

I'm asking because it seems strange to put databases in the Program Files
folder, but I don't know where else they should go.

If it matters, also assume the files are signed .accde files and the end
user will have Access 2007 Runtime installed instead of the full version.

 

[Allen Browne]

Interesting question, Jay.

The A2007 runtime installer does let the user choose the location of the
file, but here are some factors that could affect the decision.

a) Vista virtualizes the Program Files folder. So a file in this location
can disappear when a different user logs in.

b) In a corporate environment, you may find that users don't have full
permissions for C:\YourFolder. You may need to use %HOMEPATH%

c) If you expect multiple users, do you really want to install the back end?
It probably needs to be on a network, where you cannot guess the location.
More importantly, you can't chance overwriting an existing data file when
another user is added.

 

[a a r o n . k e m p f]

FrontEnd should be convered to an Access Data Project

BackEnd should live entirely on SQL Server


you'll have a lot less problems that way, without having a database
server-- with real locking and performance enhancements-- you're just
asking for trouble

 

[Tony Toews [MVP]]

Is there a "Best Practice" for file location(s) when deploying Access 2007
applications?

Please ignore Aaron Kempf's posting as he is monomaniacal on the
subject of SQL server and ADPs. That said my comments would apply
equally to ADPs.

For example, what about a split database application on one PC. Where
should the "Front End" (forms, code, etc) file go, and where should the "Back
End" (tables) file go? Is it different for Vista than for XP (ignoring other
Windows versions for now)?

In my opinion the FE and associated files such as Lebans PDF dlls
should be installed in the users Application Data\Your app name
folder. The BE, and associated files, should be installed in the
users My Documents\Your app name folder.

These files should never be installed in Program Files as standard
computer users, rightfully so, only have read only access.

Also this approach means that if the user already has a suitable
version of Access installed on their system they don't need to be an
administrator to install your app.

I've been using an Inno scrap based on Albert Kallal's work for my
purposes. Download and install the Granite Fleet Manager V1.62 Setup
http://www.granitefleet.com/download.htm for an example of what I've
done.

I'm asking because it seems strange to put databases in the Program Files
folder, but I don't know where else they should go.

Absolutely correct.

If it matters, also assume the files are signed .accde files and the end
user will have Access 2007 Runtime installed instead of the full version.

No, it doesn't matter.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

The BE, and associated files, should be installed in the
users My Documents\Your app name folder.

Thus, should be user then want to do a network install you just tell
them to drag and drop the My Documents\Your app Name folder on the
file server. And then your FE should find the BE none accessible,
prompt the user for the new location of the BE and relink the tables
automatically.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[a a r o n . k e m p f]

Please ignore Tony

He thinks that just because _HE_ is too ****ing stupid to use a
database engine wiht a future-- he thinks that somehow it's
inconcievable that there is a better platform.
Of course, SQL Server didn't become the worlds most popular database
for no reason at all--

Jet is just too complex for simple databases.
You don't need 3 tiers of Jet databases-- SQL Server does all of the
work for you.

-Aaron

 

[a a r o n . k e m p f]

wow dude, that sure sounds secure.

How _DO_ you secure Jet, anyways Tony?
From what I heard, they removed ULS from Jet because only a ****ing
retard would think that it helps.
Only a ****ing retard would use Jet.

SQL Server won the war-- so sorry that you had trouble on your _ONE_
upsizing experience.

**** you for having the audacity to think that your way is the _ONLY_
way.
**** you you egocentric ****ing dipshit..

-Aaron