Can I develop an Access App in Office 365 on one PC and run/modify it on another PC using Off 2016

[jarena]

Can I develop an Access Application in Office 365 on one PC and then successfully run/modify it on another PC using Off 2016 and vice versa?

[June7]

Should be able to. Sometimes a later version of software offers capabilities that cannot be handled by older version. For instance, I use Access 2010 and cannot handle Modern Charts introduced later. So have to design for backwards compability.

[Micron]

Office 365 is just a fee based service. I'm using it and have Access 2016 while others using 365 have Access 2019.
You could research Access versions and see what features might have been introduced in 2019 (if any) and decide whether or not there might be compatibility issues if you use them. Pretty sure others have posted 2019 db's here when seeking help and that I've been able to open them. That only proves that their db didn't use any such feature, not that there are none that might be an issue.

[jarena]

Is there a way find out if you have Office 2016 or 2019 via Office 365? In Access, I went to File --> Account and Office 365 is displayed. I then went to About Access and it displays Microsoft 365 MSO (Version 2112 Build 16.0.14729.20224) 32 Bit as well as a Product ID and Session ID, but no indication of 2016 or 2019.

[Micron]

Pretty sure Build 16 is Access 2016. This is easy enough for you to Google to find how to determine your Office version? It's what I'd do if I didn't already know.

[jarena]

An update on the Office 365/2016 Question . . . I opened a chat session with a Microsoft rep and asked him several questions. I asked about forward and backward compatibility between Access in Office 2019 and 2016 and he stated the following:

"Microsoft 365 is different that Office 2016 and 2019 and even 2021. But they are all Microsoft Office applications. Office 2016, 2019,and 2021 are Perpetual Office licenses, While Microsoft 365 is a subscription based license."

While I understand that Microsoft 365 is a subscription based license (Micron pointed this out), it didn't make sense the way it was used in the context of the sentence . . .

I also asked the rep if I develop an Access database application on my desktop (Office 365) and then copy it to the other PC running Office 2016, will it work or will I run into problems? I do not plan on using much VB code.

He replied "I have checked my resources and yes you can copy it to another computer that is running with Office 2016 version and it will work as long as there is not Macro and VB code on it."

The is a good chance that the application may have a couple of small snippets of VB code and one or two macros . . . I guess I can chance it and if I run into problems, I'll rewrite that portion of the code on the Office 2016 PC . . .

[Welshgasman]

He replied "I have checked my resources and yes you can copy it to another computer that is running with Office 2016 version and it will work as long as there is not Macro and VB code on it."

Talk about hedging your bets

I can confirm with my 2007, that a lot of times I cannot even open a database I have downloaded to help someone from a later version, and even when I can, there are new commands/options that 2007 does not recognise.

Someone asked a similar question on another forum and a link was posted by a well respected Access developer.
Have a read.
https://www.devhut.net/access-the-go...f-development/

[Micron]

This shows I'm using 365, but 365 what? Note that it says "Access for Microsoft 365 MSO" - MSO being MicroSoft Office.
To repeat, it says "Access FOR 365, not that my Access version is 365.




This would suggest that 365 applies to Office (not Access per se) and that my Access version is 16


I think you got less than a quality answer, but that's just my opinion.

[jarena]

Good link Welshgasman - thanks. The author of that article seems very knowledgeable and also provides many other helpful links as well.

[jarena]

I agree with you assessment Micron, including your last sentence.