I support a proprietary application that executes using Access 97 runtime. Typically, if a user has Office2000 installed, I have them move the 97 dlls and exe file to a sub-folder, then change the icon target to launch 97 /runtime using this path.As a rule, it works.
I have a user who has loaded his own Office2000 upgrade (to an OEM 97 machine), and every time we try to change the target statement, Windows inserts the “normal” path to Access 2000 (c:\Program Files\etc). I had him pull Office from the Startup folder, still no go.
My next thought is that there’s a registry problem, but I’m hoping that I may have overlooked something obvious so I can avoid taking the user into regedit. Is there something he may have done during the upgrade that would cause this?
appreciate your time…