Where to install .mdb

[Guest]

Access 2003. Many users use the Access Runtime.

I've historically installed my .mdb files to c:\program files\MyDirectory
However this causes problems with Vista virtuallizing and doing "funky"
things. It was suggested that I not use the Program Files directory for my
install. Using the Access 2003 Developer Extensions allows for installation to
"Program Files" All users
"UserAppData" Current user
"Desktop" Current user
"Common Appdata" All users
"My Documents" Current user
"Common Files" All users

The "common files" goes to c:\program files\common files\,
whereas "Common AppData" goes to C:\documents and settings\all
users\application data\.

As I want the pgm available to all users, I narrow the possibilities to the
3 "all users" options. Both "Program Files" and "Common Files" install into
the "program files" directory. Which leaves only the "Common Appdata".
However, when trying this on my test system for a "Limited Account" user, I'm
informed that the .mdb is read only. Am I running into a directory issue, or
something else? The Application Data directory is a hidden directory, is
there some kind of write restriction to this directory. I didn't have this
problem when using the program from the "program files" directory. The exact
error is "Cannot update. Database or object is read-only."

Do I need to re-read "Catch-22"?

thanks for input,
James

 

[Stefan Hoffmann]

hi James,

I've historically installed my .mdb files to c:\program files\MyDirectory
However this causes problems with Vista virtuallizing and doing "funky"
things. It was suggested that I not use the Program Files directory for my
install.

This was also a bad habit under XP. There exists a guide somewhere on
MSDN, but I don't have the link at hand.

As a MDB is a document, I would place it under \Users\Public\Documents.


mfG
--> stefan <--

 

[DL]

Just my thought;
Its possibly more a Vista permissions issue, as MS locked Vista down in many
ways.
You might cross post also to a Vista group for info on permissions

 

[Stefan Hoffmann]

hi James,

Do I need to re-read "Catch-22"?

http://msdn2.microsoft.com/en-us/library/bb530410.aspx

and finally I found it:

http://download.microsoft.com/downl...-9b50-3392e9886084/VistaFileSysNamespaces.pdf


mfG
--> stefan <--

 

[Tony Toews [MVP]]

As I want the pgm available to all users, I narrow the possibilities to the
3 "all users" options. Both "Program Files" and "Common Files" install into
the "program files" directory. Which leaves only the "Common Appdata".
However, when trying this on my test system for a "Limited Account" user, I'm
informed that the .mdb is read only. Am I running into a directory issue, or
something else? The Application Data directory is a hidden directory, is
there some kind of write restriction to this directory. I didn't have this
problem when using the program from the "program files" directory. The exact
error is "Cannot update. Database or object is read-only."

I had a similar problem when working with the Auto FE Updater in
Windows Vista. Thus I'm now recommending everyone work in the
"UserAppData" Current user folder for Access MDBs/MDEs.

I realize you want everyone to have the app. Using All Users is
practical for software which is installed by Admins. But that folder
isn't practical for Access MDB/MDEs which are typically much more
frequently updated and furthermore updated by users using tools such
as the Auto FE Updater.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

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/

 

[Guest]

So if you install as "UserAppData", does each user on the computer have to
install the program? Then delete all backends but one?

James

 

[Tony Toews [MVP]]

So if you install as "UserAppData", does each user on the computer have to
install the program?

Yes. Although this depends on the definition of program and what you
are using to do the install.

If by install you mean the Access runtime that only needs to be
installed once by an administrator. If by your FE MDB/MDE along with
some shortcuts then yes each user would have to do the install.

Then delete all backends but one?

Ah, so the backend isn't on a server. I had made that assumption. My
apologies. That does get a lot trickier then and I'm not sure what
the best answer is. Or even if there is an answer.

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]]

http://msdn2.microsoft.com/en-us/library/bb530410.aspx
and finally I found it:
http://download.microsoft.com/downl...-9b50-3392e9886084/VistaFileSysNamespaces.pdf

Thanks for locating those. The first page or two of the first URL
explained some things about why an administrator still has to click on
the UAC to do some things.

The second URL mentions c:\ProgramData "All application data that must
be shared among users on the computer should be stored within the
C:\ProgramData folder location." Which, of course, doesn't exist in
Windows XP and thus not going to be an option in the Access 2003
runtime setup.

That said an administrator should be able to create that folder in
Windows XP. Trouble is it won't be accessible by the users unless
permissions get changed. Which you should be able to do with a lot of
work inside an Access/VB program, which I've done for another app, or
a few pages of documentation along with screen shots. <sigh>

And do you think the users will successfully be able to add the
permissions required? Yup, not a snowballs chance in heck.

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/

 

[Guest]

Tony thanks for the responses,

I use the Access 2003 Developer Extensions to install from. This installs
the Access runtime as well as my directory containing my files including the
FE and BE. I have no control over how the program is set up (as I don't
install them) but I'd estimate that at least 90% of installs are on a single
computer (this comes from the lack of questions I've gotten on setting up on
a network). These are installed by different companies scattered across the
US. I don't really know though how many users on a single computer will use
the program, thus my wanting the program to be set up for all users.

If you'll check my original post, it shows the choices I have within the ADE
for directories. Apparently none of the choices the ADE gives me are good
choices and it doesn't allow for me to specify a custom directory (that I can
tell). The user can do a custom install and choose a directory, but that is
not a good solution.

I'm surprised that there is not a directory available within the IDE for all
users which is not either "program files" (not typically backed up by backup
software, and virtuallized within Vista with other problems I've run into) or
"application data" (hidden and read only for limited users).

Any new ideas?

James

 

[Ian Hinson]

The second URL mentions c:\ProgramData "All application data that must
be shared among users on the computer should be stored within the
C:\ProgramData folder location." Which, of course, doesn't exist in
Windows XP and thus not going to be an option in the Access 2003
runtime setup.

That said an administrator should be able to create that folder in
Windows XP.

I would have thought that a path macro such as $(Common AppData)
would be evaluated at run-time by the setup program. So, while it may
equate to "c:\Documents and Settings\All Users\Application Data" on
Windows XP it may automatically equate to "c:\ProgramData" on
Vista (if that's the appropriate path) - without any special action
being needed by the user/administrator installing the program.

Isn't that the purpose these path "macros" in the first place?

Ian.

 

[Guest]

Ian,
It is possible that AppData is relative depending on the operating system. I
don't have a Vista system to try it on. But as my 3 options all turn out to
be bad as 2 land in the \program files\ directory which causes problems for
Vista and the 3rd option being "application data" which is hidden and read
only for limited users on XP, though it may not be for Vista.

I'm wondering if anyone is using the 2007 ADE and what options are available
on it.

thanks,
James