[AccessD] Access 2021 accde (64 bit) incompatible with Access 2013 64 bit

John Colby jwcolby at gmail.com
Tue Dec 28 18:27:15 CST 2021


Did that fix the problem?

On Tue, Dec 28, 2021 at 9:15 AM Ryan W <wrwehler at gmail.com> 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.
>
>
>
> On Mon, Dec 27, 2021 at 9:27 PM Stuart McLachlan <stuart at lexacorp.com.pg>
> wrote:
>
> > It's ever been thus.
> >
> > Opening an accee with  that's been compiled with a more recent version
> > than you are
> > using.opening it with is frequently problematic.
> >
> > You need to compile on the lowest version that will be using it.
> >
> >
> >
> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458
> >
> > c-a673-102dc34bf14fhttps://
> support.microsoft.com/en-us/office/deploy-an-access-applicatio
> > n-7bb4f2ba-30ee-458c-a673-102dc34bf14f
> > <
> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14fhttps://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14f
> >
> >
> > Important   Users can't open a compiled binary file by using an earlier
> > version of
> > Access than the version in which it was compiled if the earlier version
> > doesn´t
> > support a feature added in the later version. To resolve this issue,
> > compile the
> > binary file in the Access version your users have installed.
> >
> >
> >
> > On 27 Dec 2021 at 20:15, Ryan W wrote:
> >
> > > I´m not changing bitness. Last week I was using 2013 64. This week
> > > 2021 64.
> > >
> > > None of my desktop clients use 32 bit access anymore.
> > >
> > > Unfortunately the accde file saved under 2021 doesn´t work on 2013
> > > with the same bitness. It throws some errors on startup they weren´t
> > > there with the 2013 saved accde from last week before I upgraded.
> > >
> > > Sent from my iPhone
> > >
> > > > On Dec 27, 2021, at 8:02 PM, John Colby <jwcolby at gmail.com> wrote:
> > > >
> > > > can you do a decompile / compile under the Office 2021 32 bit
> > > > compiler? Send the resulting file to those clients still on 2013.  I
> > > > think the "Bitness" of the compiler is exactly the problem.  A 64
> > > > bit compiler is going to make fundamental changes to pointer lengths
> > > > etc. You might have to run a virtual machine where you install a 32
> > > > bit version of Office 2021 so you can do the compile under the 32
> > > > bit compiler.
> > > >
> > > >
> > > >
> > > >> On Mon, Dec 27, 2021 at 6:35 PM Ryan W <wrwehler at gmail.com> wrote:
> > > >>
> > > >> We're upgrading to Office 2021, I made a small change to a form to
> > > >> fit better with the new UI (the runtime ribbon is a bit taller for
> > > >> some reason) in one of my forms which fixed the form issue for a
> > > >> user currently running Access 2021.
> > > >>
> > > >> However, users who are still on 2013 during this rollout are now
> > > >> getting 2467 coming out of a JIT class John Colby assisted with,
> > > >> and a ribbon button that simply calls DoCmd.OpenForm "MyFormName"
> > > >> now errors out with a vague message.
> > > >>
> > > >> Literally nothing in the DB changed aside from the one form, a
> > > >> decompile, compile then compact&repair and a recompile into an
> > > >> accde and distributed.
> > > >>
> > > >> I've since remedied the update mechanism I use to split 2013 and
> > > >> 2021 accde's into different directories on the server for them to
> > > >> pull down and use... but was curious if anyone had any clues?  I'm
> > > >> not moving across bit-ness or any major changes, no function calls
> > > >> that are erroring out rely on conversion to 64 bit (PtrSafe etc).
> > > >>
> > > >> Shouldn't this front end still function under an older version
> > > >> granted I haven't changed anything that should be a show stopper?
> > > >>
> > > >> The form I changed isn't even the form that the errors on open
> > > >> reference either....
> > > >>
> > > >> The challenge in debugging now is that I do not have an active copy
> > > >> of Access 2013 64 bit that allows for development. Only runtime
> > > >> environments for 2013. -- AccessD mailing list
> > > >> AccessD at databaseadvisors.com
> > > >> https://databaseadvisors.com/mailman/listinfo/accessd Website:
> > > >> http://www.databaseadvisors.com
> > > >>
> > > >
> > > >
> > > > --
> > > > John W. Colby
> > > > Colby Consulting
> > > > --
> > > > AccessD mailing list
> > > > AccessD at databaseadvisors.com
> > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > Website: http://www.databaseadvisors.com
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
John W. Colby
Colby Consulting


More information about the AccessD mailing list