Access 2003 and the bizarro world of Vista

[Ron Hinds]

Our Access 2003 app behaves very strangely running on Vista. We install to
\Program Files\AppName, where, in a "standalone" installation, both the FE
(.MDE) and BE reside. After reading through several other posts, I think the
BE problems (old data showing up, chenges not being recorded, etc.) are
related to the "virtualization" issue. If I move the BE out to a new folder
I create on the root, will that solve the virtualization issues?

Next problem is with the FE. We use a lot of temp tables in the FE to
improve performance. This has a tendency to cause the FE to bloat, as the
temp tables are constantly delted and repopulated. So I've set the
CompactOnClose flag. This fails even though I've set full permissions for
everyone to the folder and all files and subfolders. The message is "Cannot
delete garageIQ.mde - saving compacted database as dbN.mdb" where N is a
number from 1 to ? I can't see any of these dbN.mdb files in the \Program
Files\AppName folder using Windows Explorer. But, I *can* see them from an
Open File dialog box that my app creates! Is there anything, short of
sacrificing a chicken (a suggestion I saw in another post ;-) can I do about
this?

 

[Stefan Hoffmann]

hi Ron,

Our Access 2003 app behaves very strangely running on Vista. We install to
\Program Files\AppName, where, in a "standalone" installation, both the FE
(.MDE) and BE reside. After reading through several other posts, I think the
BE problems (old data showing up, chenges not being recorded, etc.) are
related to the "virtualization" issue. If I move the BE out to a new folder
I create on the root, will that solve the virtualization issues?

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

I would put it into the Public folder, cause an Access application is
"just" an Office document.


mfG
--> stefan <--