[AccessD] Converting from Access 2007 to 2016

[Jim Dettman]

Janet,

One other caution; I *hope* they are sticking with Office in 32 bit mode and
not using the 64 bit version.

Starting with A2010, Office can come two ways; 32 and 64 bit.

 64 bit doesn't buy you much, and you loose a lot.  You also can't mix 32
and 64 bit components (say Access 32 bit and Excel 64 bit).   It's either
one or the other.   

 Last, make sure they are aware that you cannot mix Office 365 Click to Run
install and traditional MSI installs.

 Again, one or the other.  For example, you can't get Office 365 with
everything but Access, then install Access as a standalone product with a
MSI install.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim
Dettman
Sent: Thursday, March 16, 2017 07:33 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Converting from Access 2007 to 2016

Janet,

 Moving from 2007 to 2016 you should find a fairly smooth process.

 However starting with A2013, a number of features were removed:

1. dbf support
2. support for Jet 3.x DB's
3. e-mail data collection feature
4. ADP's

 are the high points.   The rest are covered here.

https://support.office.com/en-us/article/Discontinued-features-and-modified-
functionality-in-Access-2013-BC006FC3-5B48-499E-8C7D-9A2DFEF68E2F

 If your not using any of those features, then you'll be fine and it will be
painless.

 On references, as long as you continue to have A2007 folks, continue to
develop in A2007.  The basic references that Access uses will automatically
"up version" when opened with A2016.   You cannot do the reverse however;
develop in A2016 and have someone with A2007 open the DB.  The references
will not automatically down version.

  If you set references beyond those basic ones (ie. Outlook), then you'll
need to be careful.  Late binding is the best as the others have said, but
if you wanted, you could maintain two versions of the app while converting
everyone.  Late binding does give a performance hit of about 15%, but that's
the route most go anyway.   With late binding, you can continue to develop
one version in A2007 for everyone.

 Of course before you try anything, make sure your apps compile cleanly in
2007 and save off copies of everything.

Jim. 

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Janet Erbach
Sent: Wednesday, March 15, 2017 04:52 PM
To: Database Advisors
Cc: Michael.Zimmer at federalmogul.com; Steve Erbach
Subject: [AccessD] Converting from Access 2007 to 2016

Hello all.  My company is still on Office 2007, but the mandate came down
last week that everyone will be upgraded to 2016.  The licenses have been
purchased and deployed, and we're supposed to upgrade everyone ASAP.

I've had issues in the past with mis-matched references:  I upgraded to
Outlook 2010, for example, to try and cure some outlook woes I had.  But
when I made changes to one of my access apps, it 'broke' on the end-user's
computer:  the reference to the Microsoft Office Object Library 14.0
couldn't be found on the user's machine because they were still on the
version with Object Library 12.0

Can you give me some guidelines for how we go about making this upgrade as
gracefully as possible?  It's going to take us a good week to update the
users/computers that need to be upgraded, and I KNOW we're going to have
instances with references mis-matches before everyone can be brought to the
same version of office.  And I suspect that we'll also have VBA code issues
with some of the Excel apps we have out there - antiquated code that uses
functions or references that won't work in 2016.

Any suggestions for us?  Please????  Thanks.

Janet Erbach
Federal Mogul
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com