OS Compatibility?

[davidg47]

I am in some of the final stages of writing an Order Management application in Access 2000. To get started, I used the Order Entry template that comes with Access. When I first started this development, I was writing it in a Windows XP Home Edition OS. But, when I tried to open the application on a Windows 2000 Pro machine, the forms would open, but none of the fields or even text would show. It was just a blank form. But, if I opened the Access application on another Windows XP Home Edition machine, everything operated normally. So, I changed my OS on the machine I'm using to write the Order Management application to Windows XP Pro thinking it might make a difference. But now when I try to open the application on the Windows XP Home machine, it prompts me for the 25-character product key to the XP Professional with Frontpage. This stuff has me going in circles. Does anyone know how to make an application developed in Access 2000 cross platform compatible?

 

[llkhoutx]

Your problem might has to do with required reference files being in different folders on each PC. Very seldom are enterprise PCs clones on one another.

 

[davidg47]

OS compatability

Thanks for your reply. So how do I fix this problem? The company I am doing this for has numerous operating systems. So I need a fix that will work across anything from Windows 95 all the way up to Windows XP Professioanl.
Thanks again,
David Greene
admin@mindinthesky.com

 

[llkhoutx]

My experience is you have to do this on each PC, as there is no code that I know of to do this programmatically. This also assumes that you have distributed an mdb, not an mde.

To check for unsatisfied references, open a form or module and go to the VBA code, then check Tools/References. Unsatisfied referenced will be marked as "Missing." Use the browser button on that form to search for the missing file. I'd first use Windows Explorer to find the file so that you can go right to it. Keep track of where it is as some PC may be clones of one another.

Another solution is to distribute a "runtime" version of your program, which entails purchasing the Window Developer for whatever version of Access you're using. Search this forum for "runtime" issues before you start.

Another thought, the various verions of Access are not interchangeable. Developing in one version doesn't mean that the program will automatically run in another version, even thropugh you've used a version converter.

Maybe somene else has other insight.