Vista I/O

[JamesDeckert]

I've got a DB using Access 2003 which I distribute with the 2003 runtime. It
is set up with a front end and back end. I've had a handful of users move to
Vista and I've seen weird I/O issues several times now. It acts like Vista
buffers changes in memory but the changes are not flushed to the hard drive.
I just talked to a user who has been using Vista for 3 weeks. While I was on
the phone with him, his data (FE and BE) reverted back to a 4 month old
version when he opened the pgm from the desktop.

I've also run into the directory I use being set to read only and when the
DB is used and changes made to the data in a form that no errors occur.
Sometimes you can exit the pgm and open again and the changes would still be
there, but sometimes the changes would disappear and revert back to the
original values with no changes. I'd have the user make changes to the data
and watch the date modified of the back end and the date modified wouldn't
change.

Anyway, every time a user goes to Vista I have these weird I/O issues. I may
have to break down and spend $500 to buy a computer I don't need with Vista.

Have you heard of any of these issues and how to resolve them?

Thanks,
James

 

[Albert D. Kallal]

(e-mail address removed)...

his data (FE and BE) reverted back to a 4 month old
version when he opened the pgm from the desktop.

Hum, that does not sound right at all. How can it go back?

However, if your placing your data files in the users *program* directory,
there is the possbility
Of some type of file virtualization occurring here.

I don't think it's your problem but you could check of the following
information:

http://support.microsoft.com/kb/927387

Have you heard of any of these issues and how to resolve them?

As mention have not heard of these issues, however do be aware that you
don't want install the backend or data file in the program directory
structure.

This much means that c:\program file\You data is off limits.

 

[Allen Browne]

The virtualization issue Albert pointed you to could account for the weird
behavior of suddenly reverting to the wrong thing (e.g. when the user logs
in as someone else.)

If both the front end and back end are Vista, there is also an IP6 issue
that could be causing you grief:
http://support.microsoft.com/?kbid=935370

 

[JamesDeckert]

Thanks Albert,

You are right. c:\program files\ is where my .mdb's land. 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" looks like it 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, should I be using "common
AppData"? When I first set this up, "documents" didn't seem like the right
place as the .mdb fits more into a "program" than a "document".

thanks again for the input.

James Deckert