[AccessD] Access 2021 accde (64 bit) incompatible with Access 2013 64 bit
jamesbutton at blueyonder.co.uk
Tue Jan 4 13:30:25 CST 2022
Do the files need 'registering' for use on those machines
Are they the same version as you have - MDF5 hash value?
Properties reports the "version" - but as that is a developer input value, that may not actually have been changed when the file content did
From: AccessD <accessd-bounces+jamesbutton=blueyonder.co.uk at databaseadvisors.com> On Behalf Of Ryan W
Sent: Tuesday, January 4, 2022 4:40 PM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Access 2021 accde (64 bit) incompatible with Access 2013 64 bit
Okay still running into this issue but in a different way:
Older Windows 7 workstations 64- bit. Running Office 2013 (32-bit)+ Access
2013 Runtime (32-bit). Compiled on Windows Server 2019 (64-bit OS) +
Office 2013 (32-bit)
Same 2467 error with the JIT classes and the same wonky error with my
RibbonOpenForm code. I can run the ACCDB error free, but the compiled
ACCDE throws errors only on these Windows 7 (64-bit), Office 2013(32 bit)
Since they run the runtime I cannot open the VBA editor to check for
missing references but the referenced libraries on the development machine
exist on the workstation in the same physical locations on the disk.
So we're on the same version of Access, same bit-ness but these older
machines are throwing a tizzy?
On Wed, Dec 29, 2021 at 7:18 AM Jim Dettman <jimdettman at verizon.net> wrote:
> << What’s the skinny on the ODB handling? >>
> It's in here:
> about halfway down.
> Monaco was delayed, but there still have been improvements made to the
> query editor. There is now a find and replace feature, and you can
> directly open a table in either view (data or design), or choose "Size to
> Fit" in the shortcut menu so you can see the full table name and fields.
> That’s covered here:
> and you can view a demo of those new features here:
> << The rest I knew about but still find that minimal for 8 years of
> development time between 2013 and 2021>>
> There are other things as well, like the graphs and a lot of minor
> things you might not notice, like wider clickable areas in some of the UI
> Access 2016 didn't have much (most of the changes there were not
> visible), but everything since that has added significant features that you
> do and I would not say they are minimal.
> -----Original Message-----
> From: Ryan Wehler
> Sent: Wednesday, December 29, 2021 7:53 AM
> To: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Cc: Jim Dettman <jimdettman at verizon.net>
> Subject: Re: [AccessD] Access 2021 accde (64 bit) incompatible with Access
> 2013 64 bit
> What’s the skinny on the ODB handling? The rest I knew about but still
> find that minimal for 8 years of development time between 2013 and 2021.
> We’ve yet to see the Monaco editor that was promised this year, too.
> Not sure I call the giant red streak along the top (since 2016?) much of a
> UI refinement. In fact I had users come ask me how to get rid of it
> > On Dec 29, 2021, at 6:18 AM, Jim Dettman via AccessD <
> accessd at databaseadvisors.com> wrote:
> > Yes, along with support for DateTime2 in SQL, more robust ODBC connection
> > handling, a new Linked Table Manager, UI refinements, numerous
> > in the SQL Editor, and quite a number of other things.
> > Access has not been standing still by any means.
> > Jim.
> > -----Original Message-----
> > From: AccessD On Behalf Of Stuart McLachlan
> > Sent: Tuesday, December 28, 2021 7:13 PM
> > To: Access Developers discussion and problem solving
> > <accessd at databaseadvisors.com>
> > Subject: Re: [AccessD] Access 2021 accde (64 bit) incompatible with
> > 2013 64 bit
> > One major difference between 2013 and 2021 is the LargeNumber/BigInt data
> > type
> > introduced in 2016.
> >> On 28 Dec 2021 at 8:15, Ryan W wrote:
> >> Okay fair enough. Your link does say that but Access has been so stale
> >> on the development front for some time that the differences between
> >> 2013 and 2021 are minimal AT BEST.
> >> I've installed Access 2013 64-bit on a VM and compiled it. I guess
> >> this will have to work for now.
More information about the AccessD