[AccessD] Upgrade from 2003 to 2019

[Paul Hartland]

Would agree with Rocky there, very few problems if avoiding system calls
and APIs, but if mixing versions of Access it can be a pain with the
references, had it several times in a company I worked for a few years back.

Paul

On Sun, 12 Apr 2020, 22:24 rockysmolin bchacc.com, <rockysmolin at bchacc.com>
wrote:

> I went up from mdb to accdb (and de) on several client DBs with very few
> problems.  But I always coded as simple as I could - no OS calls, no APIs
> if I could get away with it - things that break when you move to a new
> version of Access r a new OS.
>
> So that would be my only caveat.
>
> If they're going to run 32 and 64 bit mixed systems then they'll need two
> dbs.  And if they'[re going to mix versions of access on different clients,
> they'll run into reference problems when a DB compiled on a later version
> tries to run on an earlier version.  It seems to work the other way -
> earlier to later relinks the right library version; later to earlier does
> not.
>
> That's what I know.
>
> r
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Susan Harkins
> Sent: Sunday, April 12, 2020 1:42 PM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Upgrade from 2003 to 2019
>
> A reader wants to upgrade a split mdb to 2019. Has anyone tried this?
>
> Susan H.
>
> --
> 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
>