I have created an Access 2002 package that's being distributed out in the field. Everything has been going pretty smooth with the installations except for one where the client installed it and it wound up overlaying an existing instance of Access 97 runtime that was in use by another app.

I know there are 3rd party tools (SageKey) that address this issue, but I was wondering if anyone has ever tried customizing the Access Packaging wizard to recognize an existing runtime & either abort the install or do something else instead of tromping on it (like a bull in a china shop).

Thanks in advance!