I plan to use XP Access Developer to create an application for distribution in the commercial market. Customers who purchase the software may have XP but more likely will have earlier versions.
I am aware that there is a conflict if a XP Runtime is installed on a PC with earlier versions of Access and databases built in these earlier versions. The conflict apparently derives from the registration of the Runtime. When it is registered on a PC that already has an earlier version of Access installed, then there are two possible Jet engines that might be invoked against an Access file. I also understand that the registry will continue to use the same jet engine until explicitly told to use a the other one by providing a full filepath to it.
Thus, my understanding and partial experience is a scenario like this. You have Access97 installed then you purchase and install a XP Runtime application. After running the new application, if you attempt to open an A97 dB, an error is returned (I cannot remember if it is an offer to convert the dB to a newer version or another kind of error). Or if you open the Access97 Jet engine explicitly, then next attempt to open the runtime will be by that A97 engine and will return 'unrecognizable format".
I believe most of the above is correct, but it has been so long since I worked with XP Developer, I would not state perfect accuracy. My question is, has anyone gotten around this problem and if so, how did you do it?
Regards, Sorrells
I am aware that there is a conflict if a XP Runtime is installed on a PC with earlier versions of Access and databases built in these earlier versions. The conflict apparently derives from the registration of the Runtime. When it is registered on a PC that already has an earlier version of Access installed, then there are two possible Jet engines that might be invoked against an Access file. I also understand that the registry will continue to use the same jet engine until explicitly told to use a the other one by providing a full filepath to it.
Thus, my understanding and partial experience is a scenario like this. You have Access97 installed then you purchase and install a XP Runtime application. After running the new application, if you attempt to open an A97 dB, an error is returned (I cannot remember if it is an offer to convert the dB to a newer version or another kind of error). Or if you open the Access97 Jet engine explicitly, then next attempt to open the runtime will be by that A97 engine and will return 'unrecognizable format".
I believe most of the above is correct, but it has been so long since I worked with XP Developer, I would not state perfect accuracy. My question is, has anyone gotten around this problem and if so, how did you do it?
Regards, Sorrells