Answers inline below.... >Have you tried running the application on a PC without ANY version of >Office installed?
Yes. But it doesn't work since it's a database (.mdb) file and it looks for a program associated with that. >If the application runs w/o Office installed try >running the application after installing all MS Office applications >EXCEPT MS Access. If that works then you can either: > >1. Leave the system set up without MS Access installed. This works if >your customer doesn't need MS Access for any other application. > >2. See if there is some way to install/configure MS Access so it >doesn't try to automatically upgrade existing databases. That's never been a problem. I sort of wish it was *the* problem since that'd be easy to get around. >If neither of these solutions are available then your customer has a >serious problem because it sounds like the vendor set up the database >application with specific user level permissions. >From what I've seen, I think the error message is a red-herring. >This means you have >to know the correct administrative user id and password for the specific >database if you want to upgrade/modify the application. I'm not trying nor is it my desire to upgrade or modify this. I just want to get it to run under Windows XP instead of Windows 2000. Maybe in some parlance, that's the definition of 'modify' but I'm not looking at it that way. >Since it >doesn't sound like the vendor provided this information to your customer >as part of delivering the system then your customer is probably out of >luck. Yeah...that's being debated by various departments and until they make a decision one way or another, I'm going to keep trying to get this working.... Larry ************************************************************************* ** List info, subscription management, list rules, archives, privacy ** ** policy, calmness, a member map, and more at http://www.cguys.org/ ** *************************************************************************
