![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
On Mar 27, 11:11*am, PW <emailaddyin... (AT) ifIremember (DOT) com> wrote: If they did a Windows Update, it's possible that they updated some Office components, which could potentially have reset some keys in the Registry. I've had this happen with my users on occasion, and having them do a re-install usually fixes the problem (we're also using the Access97 runtime). You can Google the message text, and you will see that this is a documented problem. Unfortunately, most of the fixes you'll see won't help a user with the runtime version, if I remember correctly. It's part of the challenges of having multiple versions of Office products running on the same PC. My own solution is to update my app to Access2007, which isn't a walk in the park, either, at least as far a my app is concerned. Ron |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Actually, this is a pretty interesting topic in and of itself, I think I may start a separate thread about this. Happy to talk about it more off the list if you'd like, too. Ron |
#6
| |||
| |||
|
|
On Mar 27, 11:11*am, PW <emailaddyin... (AT) ifIremember (DOT) com> wrote: If they did a Windows Update, it's possible that they updated some Office components, which could potentially have reset some keys in the Registry. I've had this happen with my users on occasion, and having them do a re-install usually fixes the problem (we're also using the Access97 runtime). You can Google the message text, and you will see that this is a documented problem. Unfortunately, most of the fixes you'll see won't help a user with the runtime version, if I remember correctly. It's part of the challenges of having multiple versions of Office products running on the same PC. My own solution is to update my app to Access2007, which isn't a walk in the park, either, at least as far a my app is concerned. Ron |
![]() |
| Thread Tools | |
| Display Modes | |
| |