Which: Access 2013 64-bit or 32-bit?

[onmyway]

Hi guys,

I hope you can help me.

I would like to create a distributable compiled (I think it is an accDE?) application, but I am worried about compatibility issues and the like.

But there seems to be a bit of confusion in this regard, and I cannot seem to get an appropriate answer from my research:

Which is the best Access version to use for creating an application - Access 2013 64-bit or 32-bit?



It is for creating a simple data entry application.

[June7]

Review:

https://social.msdn.microsoft.com/Fo...orum=accessdev

http://www.mrexcel.com/forum/microso...-vs-64bit.html

As noted in the first thread, compatibility issues can occur with API code and ActiveX controls. I encountered the API issue and had to modify code. We use 32-bit Access running on both 32-bit and 64-bit machines. API code originally written for 32-bit machines errored on 64-bit machines. The modification was simply adding PtrSafe keyword in API function calls.

I've never used ActiveX controls.

[orange]

Further to June's comments and links
see this

[onmyway]

Thank you for all your responses - it really does help.

It would seem that the best strategy would in either case be to make use of SQLExpress as the DB. I know this is a different question all together, but can one create a compiled application using Access as the front end, and SQl as the DB? I.e., stand-alone installation.

[onmyway]

Thank you for all your responses - it really does help.

It would seem that the best strategy would in either case be to make use of SQLExpress as the DB. I know this is a different question all together, but can one create a compiled application using Access as the front end, and SQl as the DB? I.e., stand-alone installation.

[onmyway]

Hi guys, any last suggestions and thought before I wrap this up?

[June7]

Yes, Access can be frontend interface to SQLExpress or SQLServer or MySQL or Oracle and maybe other db backends.

[onmyway]

Thanks all