V
Vel.
I have a large database which was started in Access 2K and has since been
updated to an Access 2003 file. Recently, our office got a couple of Vista
computers installed, and thats where my troubles begin.
After installing the runtime version of Access with my database, many of the
reports simply don't work. There are frequent errors and much of the code
doesn't seem to execute.
AND
Generally, when I make updates or significant changes to the frontend, I
just replace the .mdb file in the install folder with the new .mdb. When I
do this in Vista, it bizarrely doesn't make any difference. The old .mdb
continues to be used by the database even though I can't seem to find any
evidence that the old .mdb file even exists. In the end, the only way I
could get it to update was to do a new install into a new path. Even
uninstalling and reinstalling a new package with the updated file didn't
work.
Any suggestions on how to correct either of these problems?
updated to an Access 2003 file. Recently, our office got a couple of Vista
computers installed, and thats where my troubles begin.
After installing the runtime version of Access with my database, many of the
reports simply don't work. There are frequent errors and much of the code
doesn't seem to execute.
AND
Generally, when I make updates or significant changes to the frontend, I
just replace the .mdb file in the install folder with the new .mdb. When I
do this in Vista, it bizarrely doesn't make any difference. The old .mdb
continues to be used by the database even though I can't seem to find any
evidence that the old .mdb file even exists. In the end, the only way I
could get it to update was to do a new install into a new path. Even
uninstalling and reinstalling a new package with the updated file didn't
work.
Any suggestions on how to correct either of these problems?