![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Can opening the app using different Access versions, not waiting for the app to install the new Access (maybe closing it down via task manager) corrupt the app? |
#3
| |||
| |||
|
|
Salad <salad (AT) oilandvinegar (DOT) com> wrote in news:qpCdnR4PXsI3rV7WnZ2dnUVZ_rIAAAAA (AT) earthlink (DOT) com: Can opening the app using different Access versions, not waiting for the app to install the new Access (maybe closing it down via task manager) corrupt the app? I'd suggest it's likely not the app itself, but the registration of each version of Access that's the issue. The "fix-up" on the references is dependent on the application version being fully registered, and the error you report is very similar to what others have reported with incomplete registrations. I think I understand. It failed in A2003. By running it in A2007, the |
#4
| |||
| |||
|
|
David W. Fenton wrote: Salad <salad (AT) oilandvinegar (DOT) com> wrote in news:qpCdnR4PXsI3rV7WnZ2dnUVZ_rIAAAAA (AT) earthlink (DOT) com: Can opening the app using different Access versions, not waiting for the app to install the new Access (maybe closing it down via task manager) corrupt the app? I'd suggest it's likely not the app itself, but the registration of each version of Access that's the issue. The "fix-up" on the references is dependent on the application version being fully registered, and the error you report is very similar to what others have reported with incomplete registrations. I think I understand. It failed in A2003. By running it in A2007, the registration was complete. Running A2003 and allowing it to open and run thru the installation process completed its registration and so it worked. |
![]() |
| Thread Tools | |
| Display Modes | |
| |