Migrate 2013 32 to 2021 64 bit

[Mike505]

I have an Access application that was initially developed in 2017 using Access 2013 32 bit (accdb) on a laptop circa 2017. At some point that laptop will need to be replaced and I would most likely want to install the most current version of Access. If a 32 bit version is available I'd go with that since I would expect the fewest problems that way. If a 32 bit version is not available and I'm forced into 64 bit, can someone give me a rough idea of what issues I may face.



These are some of the characteristics of what I have:
1. The application is split into a front and back-end.
2. It resides on a shared drive on PC1. In some cases a user is using PC1. In other cases, a user is using PC2 that points to the shared drive on PC1.
3. There are what I would call typical forms and queries. Very few reports.
4. Some inquiries export to Excel.
5. Almost all code associated with a form is VBA code maintained via the code editor. There is very little form code that was created via macros.
6. The application will at times call batch files to do certain things.

So I guess what I'm looking for is (1) it will probably run just fine or (2) expect a fair amount of time-consuming problems or (3) let someone else do it.

[Edgar]

Here's an idea.
1. Make a copy of the backend
2. Remove sensitive data from the copy, if necessary
3. Open the system using a 64 bit version of Office.
4. Use all of the features and see what fails.
By the way, this is one of the things for which we all should have a testing module, so that we can perform all of the pre-programmed code at once instead of checking every feature one by one and why containerization is important. But Access manages these bitness changes well enough so that you don't even have to worry about either of those two things most of the time.

In my experience the only things that fail are in the VBA code. Usually Longptr related data types and ADO (?) operations that I want to perform from outside of Access.

So, if you can get your hands on a computer with the target environment, you could check there. Also, someone here might be able to help check first hand if you upload it here.

Anyway, good luck.

[Mike505]

Thanks, I would try it if I had the use of a 64 bit Access 2021 development platform but I don't.
If anyone has actually gone thru something like this, I'd love to hear about the experience.

[Micron]

Fairly certain you can work with a 32 bit created db while using 64 bit but not the other way around but you'd be wise to verify that. There are things in 64 that are not in 32, so when you think about it, a 64 bit version has everything the 32 has, but not the reverse. My understanding is that you can't open the 32 bit version, rather than Access trying to figure out whether or not you used any of those features. Suggest you google (or whatever) to understand the 64 bit version differences to decide whether or not you need any of those features and see if you can convince IT if they're in the picture, to install 32 bit Office if you'll never need them. Code isn't the primary problem because code can be modified to work in both versions if there are certain API calls. If not, it's usually not necessary.

[isladogs]

Things you will need to deal with:
1. Conversion of APIs to work in 64-bit using PtrSafe & LongPtr (as mentioned above)
2. A small number of library references do not work in 64-bit e.g. MS Flexgrid. You're more likely to have issues with external references you imported into Access
3. Some ActiveX controls do not work in 64-bit. Again more often an issue with external ActiveX controls

Conversely, you are less likely to get out of memory errors when running intensive procedures in 64-bit Access. That is one of the few real advantages of 64-bit

@Micron
You can run apps created in 64-bit in 32-bit Access provided the APIs are setup correctly
The same APIs will work in both 32-bit & 64-bit Access from 2010 onwards with identical coding

[Micron]

You can run apps created in 64-bit in 32-bit Access provided the APIs are setup correctly

Now I believe I was thinking of accde, so in those cases, what I said is true? They have to be re-compiled as 64 bit accde?

[isladogs]

Now I believe I was thinking of accde, so in those cases, what I said is true? They have to be re-compiled as 64 bit accde?

Yes. ACCDE files will only work in the same bitness they were created in