We recently converted from NT to XP and my dbs are exhibiting strange behaviors in the runtime version of access. Different applications on different machines and all references have been verified.
1. Runtime version ignores default printers while "full" version machines print to correct printer.
2. Closing two of the six forms opened from the base form cause a drop down box on the base form to go empty yet if you click on a line in the white area the patient data appears. It's like the forecolor of the dropdown area has been changed to white.
3. Clicking a command button to close the "enteractivity" form causes "enter parameter value " "forms!enteractivity!cmbBatchNo". That code isn't in the onclick for the command button and anywhere else I reference that dropdown box in code I include ".column".
And I can't reproduce these errors on my development machine even if I use /runtime. Do I have to rebuild these db's from scratch?
1. Runtime version ignores default printers while "full" version machines print to correct printer.
2. Closing two of the six forms opened from the base form cause a drop down box on the base form to go empty yet if you click on a line in the white area the patient data appears. It's like the forecolor of the dropdown area has been changed to white.
3. Clicking a command button to close the "enteractivity" form causes "enter parameter value " "forms!enteractivity!cmbBatchNo". That code isn't in the onclick for the command button and anywhere else I reference that dropdown box in code I include ".column".
And I can't reproduce these errors on my development machine even if I use /runtime. Do I have to rebuild these db's from scratch?