C
Craig
Hello,
I have an Access Database designed in Access 2003 which I have distributed
with the runtime version of Access included with Visual Studio Tools for
Office 2005.
The database works well for the majority of users, but a small number of
users encounter a runtime error (causing the database to close) whenever they
try to run/preview any reports.
The form that they are using to run these reports has error handling, but
all I get is the dreaded "Access has encountered a runtime error and needs to
close," so I am not sure what the source/cause of the error could be. I'm
additionally mystified because I don't understand why some users get the
error and others don't. I am unable to replicate the error on my own PC.
My latest theory is that it may have something to do with the version of
Access runtime --- I think the trouble users are using Access 2000 runtime
whereas the ones who don't have problems have 2003?
My questions:
1. Are there 2000 and 2003 version of Microsoft Access Runtime?
2. If so, how do I confirm that the trouble user is on 2000 and not 2003?
3. If he is on 2000, how do I force his computer to use the 2003 version?
(I had thought I included the 2003 version with the installation package, but
he has MS Office 2000 on his computer and I think that somehow it may be
drawing 2000 runtime from that?)
Any help is greatly appreciated!
Thanks,
Craig
I have an Access Database designed in Access 2003 which I have distributed
with the runtime version of Access included with Visual Studio Tools for
Office 2005.
The database works well for the majority of users, but a small number of
users encounter a runtime error (causing the database to close) whenever they
try to run/preview any reports.
The form that they are using to run these reports has error handling, but
all I get is the dreaded "Access has encountered a runtime error and needs to
close," so I am not sure what the source/cause of the error could be. I'm
additionally mystified because I don't understand why some users get the
error and others don't. I am unable to replicate the error on my own PC.
My latest theory is that it may have something to do with the version of
Access runtime --- I think the trouble users are using Access 2000 runtime
whereas the ones who don't have problems have 2003?
My questions:
1. Are there 2000 and 2003 version of Microsoft Access Runtime?
2. If so, how do I confirm that the trouble user is on 2000 and not 2003?
3. If he is on 2000, how do I force his computer to use the 2003 version?
(I had thought I included the 2003 version with the installation package, but
he has MS Office 2000 on his computer and I think that somehow it may be
drawing 2000 runtime from that?)
Any help is greatly appreciated!
Thanks,
Craig