Access 2016 Application to Access 365 - Will It Work?

[DittoBird]

Quick Question: Will an application developed in Access 2016 run in Access 365? Apart from forms and tables, there are, of course, VBA and non-standard references. The back end is Jet. What about an accde?



This link, https://www.fmsinc.com/microsoftacce...y/features.htm, seems to indicate 365 will have all the features I am used to in 2016. Our organization is forcing all of us to switch and I need to know if this will be relatively painless or if I should get a head start on frustrated throwing things around my office. LOL

Thanks in advance

[Micron]

As long as the bitness is the same, you should have no issues. If not, then maybe, and most of those issues relate to the use of API's used in 32 bit versions. They usually have to be modified for 64 bit - not a huge thing. If you have any choice or say in the matter, get them to install 32 bit version of Office. It used to be the default but M$ has made 64 bit the default without providing any escape from the issues. IMO there is no present need for 64 bit Office. In Access, it allows for a very large number type which most people don't need. AFAIC, 365 is just the new name for Office and what used to distinguish between the subscription version of Office vs the installed version. I use Office 365 with Access 2016 - but 32 bit for sure.

[June7]

Short answer: It should.

However, I have read a number of discussions of issues encountered with code errors when running in 365. You probably won't know until you try.

What do you mean by "non-standard references"?

[isladogs]

Agree with both previous answers except for one point.
Bigint datatype (very large numbers) is supported in both 32-bit and 64-bit Access from 2016 onwards.

[Micron]

Now that you've taken away my only answer to why use 64 bit at all at the present time, what reason am I left with??

[Minty]

Now that you've taken away my only answer to why use 64 bit at all at the present time, what reason am I left with??

Excel users is the answer.
1,000,000 rows instead of 64000.

[isladogs]

Now that you've taken away my only answer to why use 64 bit at all at the present time, what reason am I left with??

As fa's as 64-bit Access is concerned, it has large address awareness (LAA).... but that is scheduled to be added to 32-bit Access in the near future.
LAA can help reduce out of memory errors e.g. when importing very large text files or speed up such imports

[DittoBird]

What do you mean by "non-standard references"?

Probably a poor choice of words on my part. I meant I needed to add references apart from the ones that come referenced by default. I needed to add a couple, MS Shell Controls 7 Automation and MS Office 16.0 Objects (versus MS Access 16.0 Objects). Nothing really special.
--
Tim

[DittoBird]

As long as the bitness is the same, you should have no issues. If not, then maybe, and most of those issues relate to the use of API's used in 32 bit versions. They usually have to be modified for 64 bit - not a huge thing. If you have any choice or say in the matter, get them to install 32 bit version of Office. It used to be the default but M$ has made 64 bit the default without providing any escape from the issues. IMO there is no present need for 64 bit Office. In Access, it allows for a very large number type which most people don't need. AFAIC, 365 is just the new name for Office and what used to distinguish between the subscription version of Office vs the installed version. I use Office 365 with Access 2016 - but 32 bit for sure.

Unfortunately, it'll be 64 bit and I'm in 32 bit 2016. I wish I had a say - I've always been irritated by IT support folks when they insist on updating things without checking with some of the users trying to actually f***king do something for the organization. Though I must be fair and also explain these folks are top notch when I need help in networking and organizational software. In this case, I'm implementing a computerized maintenance management system (something I have 30+ years of experience in implementation, operation with maintenance trades, administration, and writing supplemental applications to support) to an organization that inexplicably, has never used one (which blows my mind).

Thank you very much, though, in spite of my worries, this does sound reassuring. All the best.

[CJ_London]

Not sure if it is a typo but you say that the bE is jet? Do you mean ace? Ace superseded jet with the launch of access 2007.

However if jet I doubt that will have an impact on your transition to 365

[Micron]

I worked a lot with/in a CMMS for 30 years as well. It did everything they could think of - FMEA, predictive (ICMS component), preventive, planning & scheduling, purchasing, inventory, H&S, BOM and one other component but I can't recall it's acronym or exact function. The company was known world wide for its success in predictive maintenance and they were able to partner with another company to promote that system because it was designed in house. Good luck with your rather large task!

[DittoBird]

Not sure if it is a typo but you say that the bE is jet? Do you mean ace? Ace superseded jet with the launch of access 2007.

However if jet I doubt that will have an impact on your transition to 365

Thank you Ajax. I may have the nomenclature incorrect. I was always under the impression that ACE was the version of Jet? Maybe not.

[DittoBird]

I worked a lot with/in a CMMS for 30 years as well. It did everything they could think of - FMEA, predictive (ICMS component), preventive, planning & scheduling, purchasing, inventory, H&S, BOM and one other component but I can't recall it's acronym or exact function. The company was known world wide for its success in predictive maintenance and they were able to partner with another company to promote that system because it was designed in house. Good luck with your rather large task!

Ah, kindred spirits. Haz Mat as the other component, maybe, though probably under H&S. Vehicle fleet management?

[Micron]

No, and not RCA either. I seem to recall that it was along the lines of FMEA. Whatever it was, I don't think I was ever involved in it.

[Welshgasman]

Excel users is the answer.
1,000,000 rows instead of 64000.

I have that many rows in Excel 2007 32bit?

In fact Lloyds bank only upgraded their Excel in office to 2007 for access to that many rows. The rest was 2003?