S
Sue Thomas
My client's machine running XP Home (all updates applied) and Office 2000 (SP-3) is having difficulty when displaying a popup form that is called from a main form. Their is very little code in the popup form and it' is a customized find form with a selection of different field to search by (Last Name, First Name, etc.) and a text box control. The popup form is completely unbound
The form displays the background image of the form that it is being called from and the controls on the form do not display. (It's see-through...
If I open the file from Windows Explorer, the popup form is see-through
If I open the file from a desktop shortcut, the popup form is see-through
If I open Access and then open the file the popup form displays the controls properly
If I open the file in Access, decompile and re-compile the code on the client's machine, I can open the form with no problems from Windows Explorer or the desktop shortcut
I have developed the application on Access XP (developer's edition) and plan on deploying the finalized package with a compiled version with the XP runtime. At present, we are in the testing and tweaking phase, so the client is using their copy of Access 2000 running a straight mdb file.
Are there any documented issues in regard to a Microsoft Access database created on XP and being used on an Access 2000 full version with these type of isssues? If so, what is the work around, other than the above methodology
Thank you for any assistance you may provide
The form displays the background image of the form that it is being called from and the controls on the form do not display. (It's see-through...
If I open the file from Windows Explorer, the popup form is see-through
If I open the file from a desktop shortcut, the popup form is see-through
If I open Access and then open the file the popup form displays the controls properly
If I open the file in Access, decompile and re-compile the code on the client's machine, I can open the form with no problems from Windows Explorer or the desktop shortcut
I have developed the application on Access XP (developer's edition) and plan on deploying the finalized package with a compiled version with the XP runtime. At present, we are in the testing and tweaking phase, so the client is using their copy of Access 2000 running a straight mdb file.
Are there any documented issues in regard to a Microsoft Access database created on XP and being used on an Access 2000 full version with these type of isssues? If so, what is the work around, other than the above methodology
Thank you for any assistance you may provide