compatibility of ACCDE on different PCs

[AccessNewbie2007]

Hi all, I know that the below has been discussed in a big number of topics but I am really tired of this situation...

I have an access application developed mainly under 2007 with MySQL ODBC connector enabled to connect with remote tables and later on added some features under Access 2013.

when a client request a copy, I usually ask for the OS version as well as the Access version and based on it I compile with the lowest version for example if he has MS2010 I open the 2007 version, compile it and make accde...

the main problem I am facing is that this ACCDE is not working on all PCs normally even if the target PC has office 2007 installed. here's an example:

PC1: Win 7 SP1 (64 bit) + Access 2007 = ACCDE working 100%

PC2: Win 7 (64 bit) + Access 2007 = ACCDE not working I have to add the accdb and compile it on the target pc and make the accde on that PC to work

PC3: Win7 (32bit) + Access 2007 = ACCDE working 100%

PC4: same as PC2 and working
PC5: same as PC3 and NOT working

so it is really a headache and it is not always possible and SAFE to copy the accdb on the target pc to compile it and make an accde file accordingly.

adding runtime to corresponding versions did not solve the problem at all, the conclusion after too many trials is that the copy must be compiled on the target PC which is not safe and always easy.

does anyone have a solution for similar problem? your advises are much appreciated

Thank You

 

[pr2-eugin]

Unfortunately, the compiled project should be done on specific bits. As you have already found 32 bit should be compiled in a 32 bit environment 64 bit should be compiled in a 64 bit environment.

Now VBA code is not compatible with different bit files so you have to make sure all code is made PtrSafe, to enforce they work in 32 and 64 bit environment. More info : http://www.access-programmers.co.uk/forums/showthread.php?t=243843 AND http://www.access-programmers.co.uk/forums/showthread.php?t=232052

Regarding your PC#5, See if all updates have been installed including the latest Service Packs.

 

[AccessNewbie2007]

Thank you for the reply, but PC2 and PC4 have the same specs both are running under 64bit (Win 7) and 32 bit of MsAccess 2007... honestly it is not always possible to manage to compile it on the user PC because I sometimes issue an update for the frontend so it is really a headache to manage it...

I can create two versions (with 2007 as the lowest version) one compiled under 64bit and the other 32bit but do you think there is another option?

do you think decompiling and recompiling can do the job?

 

[pr2-eugin]

I have not found an alternate solution unfortunately. I still do two compilations. One for a 64 bit machine and another for a 32 bit. The older version the better.

Decompiling and Recompiling will not solve your problem unfortunately !

 

[spikepl]

Be careful not to muddle the issue by inserting yet another variable into it, that being Office 32 bit vs Office 64-bit version. So far OP did not mention anything about Access 64 bit, so all that PtrSafe business does not apply.

(If you need to make an Access 64-bit version and have API calls, then do take care, because declaring things PtrSafe might not be enough - some variables may also need a changed declaration. MS has published a list of all calls modified for the 64-bit Access version). See http://www.access-programmers.co.uk/forums/showthread.php?t=275117 )

 

[AccessNewbie2007]

If I eliminate the 64bit option by mentioning to the clients that only 32bit is supported. and I do the compilation under Win7 SP1 with Office 32bit with the lower Access version which is in my case 2007, how can I guarantee that it will work on other PCs?

 

[spikepl]

In your first post you did not mention specifically on which syste, the accde was compiled. But your examples imply that you cannot cover all existing permutations. I do not quite see why you'd want to throw out the 64-bit windows, since your accde works on some occasions ..

Overall: why accde? If you supplied accdb then all these problems would go away.

 

[AccessNewbie2007]

but as you know supplying accdb is not safe because you are simply giving access over everything (forms, modules...) , that's why I compile an ACCDE

 

[Solo712]

but as you know supplying accdb is not safe because you are simply giving access over everything (forms, modules...) , that's why I compile an ACCDE

I have some experience with ACCDE running on Windows 64-bit (both Win 7 and 8.x) with different Service packs. I have yet to see an issue with ACCDE (A2007/A2010) compiled on a 32-bit machine running on those machines. You absolutely have to make sure however that the 64-bit Windows machines do not run 64-bit Office. It is not just a question of long pointers. The compiles of these two Office versions are simply not compatible. If the machines run 64-bit version of Windows, you will be fine as long as they have 32-bit Office installed on them. Then you can you can run 32-bit ACCDEs on them without trouble (at least I can).
Now, to install a 32-bit Office on a 64-bit Windows can be a little bit of a chore because by default the Office installs a 64-bit version of itself. With 2013, I think you have to order the 32-bit version because you don't get the media with x64 and x86 both present.

Best,
Jiri