Access Version/Build numbers

[Snowflake68]

Can anyone explain how I can tell which is the latest version of these two numbers?

16.0.732.1051
16.0.732.1054

I have built an Access application using Full version of 2013 however a couple of the end users are using Office 365 Pro Plus (Access 2016) and are having issues with the application. They report that it runs very slow and get error messages about memory issues. I have obtained a copy of Office 365 Pro Plus but my version build number is 16.0.732.1054 and I am not getting the error that the user using 16.0.732.1051 is getting.

I would first like to somehow get to use the same version as them so that I can see if I can replicate the error.

Not sure whether to tell them they need to run an update or uninstall an update.

 

[Lightwave]

The larger number is always the later version.

So 1054 is more recent than 1051

 

[Snowflake68]

The larger number is always the later version.

So 1054 is more recent than 1051

Thanks for you reply. Do you know if I am able to downgrade to 1051. I want to be on the same version as the user so that I can run tests to see if I can replicate the errors.

I can replicate the errors then I can then tell them to upgrade to see if it fixes it for them.

 

[The_Doc_Man]

The problem is that you are both on version 16.0.732 but at different patch levels. You cannot explicitly download any specific "build" of Access because they might exist in the bowels of Microsoft (along with the rest of their ...stuff) but you can bet dollars to doughnuts that you can't get to them.

You can, if you have the patch history available, try to uninstall the most recent patch and see if it gets you back to build 1051 - because that is how those build numbers are most often updated.

 

[Snowflake68]

The problem is that you are both on version 16.0.732 but at different patch levels. You cannot explicitly download any specific "build" of Access because they might exist in the bowels of Microsoft (along with the rest of their ...stuff) but you can bet dollars to doughnuts that you can't get to them.

You can, if you have the patch history available, try to uninstall the most recent patch and see if it gets you back to build 1051 - because that is how those build numbers are most often updated.

I dont have any patch history because it was a new install of the 365 Pro Plus. I have now asked the user to run an update on theirs to see if that sorts out their issues. Hopefully it will.
Thanks

 

[isladogs]

Probably not relevant here, but for info, 32-bit & 64-bit Access versions will have a slightly different build number even though they are in other senses identical.

So if you are using 32-bit & the other user has 64-bit then errors may occur if API declarations haven't been updated for 64-bit

 

[Snowflake68]

Probably not relevant here, but for info, 32-bit & 64-bit Access versions will have a slightly different build number even though they are in other senses identical.

So if you are using 32-bit & the other user has 64-bit then errors may occur if API declarations haven't been updated for 64-bit

All users are on 32 bit