[AccessD] Fwd: [dba-Tech] Using Old Ofice versions?

[Rocky Smolin]

And since I'm coming to the end of my programming career I guess I'll stick
with the 2010. But I also have always programmed with the simplest features
of Access so that I didn'trun into problems like you point out.  Simple is
also easier to maintain.

r
On Mon, Feb 20, 2023 at 9:34 AM Jim Dettman via AccessD <
accessd at databaseadvisors.com> wrote:

> Rocky,
>
>   Actually, yes, as far as the references are concerned.
>
>   You still would have issues though with features in 2021 not available in
> earlier versions, and with things like support for BIGINT in SQL and
> datetime2.
>
>   Really best to develop using the oldest version you want to support and
> come forward.  That's always been the mantra with Access development across
> versions.
>
> Jim.
>
> ----Original Message-----
> From: AccessD On Behalf Of Rocky Smolin
> Sent: Sunday, February 19, 2023 2:11 PM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Fwd: [dba-Tech] Using Old Ofice versions?
>
> That's a really good chart. I guess the answer - because of the broken
> library references going backward - is to stay with A2010.
>
> Although, if I read the chart right, an app compiled in 2021 would be
> backward compatible to 2016 - 16, 19, and 21 all being Version 16.0. But
> someone running 2013 - which is Version 15.0 - would have broken
> references.
>
> Correct?
>
> r
>
> On Sun, Feb 19, 2023 at 11:02 AM Martin <martinreid at gmail.com> wrote:
>
> > http://fmsinc.com/MicrosoftAccess/history/features.htm
> >
> > On Sun, 19 Feb 2023, 18:30 Jim Dettman via AccessD, <
> > accessd at databaseadvisors.com> wrote:
> >
> > > Rocky,
> > >
> > >
> > > << So, if I begin using Access 2021, will I have a problem with users
> > using
> > > earlier versions of Access ->>
> > >
> > >   Yes.  Biggest issue would be references.  The critical references
> will
> > > auto update to newer versions, but they will not downgrade to older
> ones.
> > >
> > >   Your 2021 won't run with at least that change being made.   This is
> > > nothing new BTW.   Going backwards has always been problematic.
> > >
> > > << Does anyone know how far back compatibility would go - to what
> version
> > > of
> > > Access, that is - if I compiled my app with 2021.>>
> > >
> > >  Outside of the references, 2013 would be about it.    From 2016 on,
> the
> > > code base is more or less the same.    The main issue is that you use
> > > something that is only in a newer version, and it doesn't exist in an
> > older
> > > one.   Then your app may break in ways you don't expect.     There are
> > > other
> > > things as well, such as the use of BIGINT, which actually modifies the
> > > database level and cuts you off from older versions (you do get a
> > warning).
> > >
> > >  Save yourself some headaches; do what you have been doing; stick with
> > > development in 2010 and bring it forward.
> > >
> > > Jim.
> > >
> > > -----Original Message-----
> > > From: AccessD On Behalf Of Rocky Smolin
> > > Sent: Friday, February 17, 2023 3:16 PM
> > > To: Access Developers discussion and problem solving
> > > <accessd at databaseadvisors.com>
> > > Subject: [AccessD] Fwd: [dba-Tech] Using Old Ofice versions?
> > >
> > > I am still using Access 2010 for development - habit - using the oldest
> > > Access as it is usually forward compatible to those using later
> versions,
> > > but not backward compatible with those using earlier versions.
> > >
> > > I have O Professional Plus 2021 and am using it for the other modules -
> > > Word, Excel, PPT. And I like them.  Nothing special about them but the
> > new
> > > interfaces are pleasing.
> > >
> > > So, if I begin using Access 2021, will I have a problem with users
> using
> > > earlier versions of Access - the problems I ran into were mostly
> > > libraries.  I use early binding and would not be happy to have to
> switch
> > to
> > > late binding.
> > >
> > > Does anyone know how far back compatibility would go - to what version
> of
> > > Access, that is - if I compiled my app with 2021. Would they run on
> 2013,
> > > for example?
> > >
> > > MTIA
> > >
> > > Rocky
> > >
> > >
> > > On Sun, Jan 22, 2023 at 3:38 PM Stuart McLachlan <
> stuart at lexacorp.com.pg
> > >
> > > wrote:
> > >
> > > > MS are going snooping  to find out if you using older versions of MS
> > > > Office :)
> > > >
> > > >
> https://www.theregister.com/2023/01/21/microsoft_office_count_update/
> > > > _______________________________________________
> > > > dba-Tech mailing list
> > > > dba-Tech at databaseadvisors.com
> > > > https://databaseadvisors.com/mailman/listinfo/dba-tech
> > > > 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
> >
> --
> 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
>