[AccessD] Converting from Access 2007 to 2016

[Janet Erbach]

Darryl - well, that is very good to hear!  I will take that attitude, then
- that the upgrade will be worth whatever tribulations I may have to endure
during the conversion.  Thank you!

On Wed, Mar 15, 2017 at 5:02 PM, Darryl Collins <
darryl at whittleconsulting.com.au> wrote:

> Hi Janet,
>
> One positive thing is that Access 2016 has been super stable and reliable,
> at least in my role and what I ask of it.  Which makes a change as usually
> Access is the lonely bastard child of the office suite and tended to fall
> over randomly and crash.  From memory, Access 2007 was less than stellar
> when it was launched.   (it has been many years since I used it - maybe it
> has gotten better over the years?).
>
> For what it is worth, I find Excel 2016 is more problematic and buggy than
> Access these days.
>
> Generally you should be good.
>
> Regards
> Darryl.
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Rocky Smolin
> Sent: 16 March, 2017 8:52 AM
> To: 'Access Developers discussion and problem solving' <
> accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Converting from Access 2007 to 2016
>
> Janet:
>
> The only sure way I know of avoiding 'broken reference syndrome' is to
> convert the app from early binding to late binding.  Then the right library
> will be referenced at run time instead of during code compile.
>
> And, in my experience, it only happens when an app's code compiled on a
> later version of Access runs on an earlier version.  So an app developed on
> 07 should run just fine on 16.
>
> Depends, of course, on how many places you are using early binding and so
> how many places the code needs to be changed.  If many, it might just be
> easier to solve the problems one at a time until everybody is on board with
> 16.
>
> I'm assuming that all the apps run on the client machine and are linked to
> a back end on the server.  In that case you might not have to do anything
> at all to your apps.  IOW, don't compile your apps on 16 and distribute.
> Just upgrade the client to 16 and run. Maybe there won't be any conversion
> needed. That sounds too easy so it probably won't work. :)
>
> How about not upgrading the apps to the client until they are up on 16?
>
> Have you tested the current 07 versions on 16 and found any problems?
>
> HTH
>
> Rocky
>
>
>
>
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Janet Erbach
> Sent: Wednesday, March 15, 2017 1: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
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>