I have a 32 bit msaccess database (2016), on various machines it runs on 32 bit access.
On one machine it runs on 64 bit access. herein sits the issue, I have declared the few API's as PTRSafe. I run the database from the 64 bit version of access complied in 32 bit and also try complied in the 64 bit version of access.
Now the issue, On a specific form (only one) that loads and runs perfectly in 32 bit, it comes a cropper in 64 bit after making a selection in a dropdown box, the database simply closes . This happens about 20 % of the time. nothing seems to be odd about the code within the after update in the dropdown box .
The code in the after update is populating a sub form with the contents of a table located in an external database that is not linked (this is done as the table chosen is very dynamic and linking via backend/front end is not viable.
It populates perfect in 32 bit and never crashes. If, in the 64 bit version of the database i open any other form, close it, then open the offending form it works perfectly every time, or if after i get the crash, reopen it it will work perfectly every time without having to open a different form first. the form is actually populating a sub form hence i tried to first populate the subform with a 'working form', then after a doevents command, populate the subform with the offending form. that doesnt help either
can anyone offer any advice as to why this might be happening, i would, sometime in the future have the database totally in 64bit but not at the moment with this happening on the only PC with 64 bit.
On one machine it runs on 64 bit access. herein sits the issue, I have declared the few API's as PTRSafe. I run the database from the 64 bit version of access complied in 32 bit and also try complied in the 64 bit version of access.
Now the issue, On a specific form (only one) that loads and runs perfectly in 32 bit, it comes a cropper in 64 bit after making a selection in a dropdown box, the database simply closes . This happens about 20 % of the time. nothing seems to be odd about the code within the after update in the dropdown box .
The code in the after update is populating a sub form with the contents of a table located in an external database that is not linked (this is done as the table chosen is very dynamic and linking via backend/front end is not viable.
It populates perfect in 32 bit and never crashes. If, in the 64 bit version of the database i open any other form, close it, then open the offending form it works perfectly every time, or if after i get the crash, reopen it it will work perfectly every time without having to open a different form first. the form is actually populating a sub form hence i tried to first populate the subform with a 'working form', then after a doevents command, populate the subform with the offending form. that doesnt help either
can anyone offer any advice as to why this might be happening, i would, sometime in the future have the database totally in 64bit but not at the moment with this happening on the only PC with 64 bit.