Upgrading from access 2010 to access 2016

[atrium]

We are considering upgrading to Office 365.
At the moment our major database application is written in access 2010, therefore I need to look at the process of upgrading the database to access 2016.
I'm sure many have been through the process I just want some tips and tricks to make the transition as smooth as I can get.
I have extensive forms with VB and links to office libraries. The application automatically integrates (via VB) with word and Outlook.

I would like to know what doesn't convert properly, what inbuilt functions in 2010 are not in 2016. What problem areas I should look at, what to watch for.

Any help would be really appreciated.

Atrium

 

[CJ_London]

I don't have any experience with office 365 but you might find the discussion on this link of interest

https://www.youtube.com/watch?v=3wdjYIby_b0

looks like tables are converted to sharepoint, vba is 'converted' successfully 99% of the time (I presume to use sharepoint since only tables are uploaded)- but there is a web compatability checker you can use to identify the issues. Tables are limited to circa 30,000 records

 

[atrium]

Do I have to go sharepoint if we use Access 2016.

Watching the video was a bit scary as I have about 96 tables in the database and heaps of VBA

I have some files with 50k+ records

Or should I go to sharepoint in 2010 and then go to 2016??

Atrium

 

[stopher]

I'm using Office 365 and Access 2016 any noticeable difference from previous versions. I can certainly store millions of records in normal accdb files. Not had any issues with any code and I have plenty of that.

 

[atrium]

Thanks Stopher your experience sounds just what I want - trouble free.

Did you have any planned strategies when migrating any of the objects.

I was thinking of creating a small version of our project and starting with that.

Thanks again for your followup

Atrium

 

[Simon_MT]

The file format accdb is 2007-2010 or 2007-2016. There are probably some more features but recent developments are on the web application side of Access. I when from 2007 to 2016 without any major problems.

Simon