[AccessD] Windows 10 & Access 2003

[David McAfee]

2016 dropped .adp support.

I had to make a bunch of changes when we upgraded to O365 over here.

On Tue, Sep 17, 2019, 11:39 AM John Bartow via AccessD <
accessd at databaseadvisors.com> wrote:

> I agree to an extent. Problem is that obsolete tech is getting left behind
> at an increasing rate.
>
> It is now standard procedure for Office 365 support to no longer support
> Outlook 2010 (because it does not support many newer email security
> requirements and MS is not going to update it to do so.) The big question -
> can Access 2010 be far behind it? Crapshoot.
>
> John Bartow
> WinHaven Consulting
>
> -----Original Message-----
> From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of Rocky
> Smolin
> Sent: Sunday, September 15, 2019 1:14 PM
> To: 'Access Developers discussion and problem solving' <
> accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Windows 10 & Access 2003
>
> I agree - Access 2010 - 32-bit.  Because it works.  And you can get them
> cheap.  I like obsolete tech.  It tends to work. :)
>
>
> Rocky Smolin
> Beach Access Software
> 760-683-5777
> www.bchacc.com
> www.e-z-mrp.com
> Skype: rocky.smolin
>
>
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> James Button via AccessD
> Sent: Sunday, September 15, 2019 7:48 AM
> To: 'Access Developers discussion and problem solving'
> Cc: James Button
> Subject: Re: [AccessD] Windows 10 & Access 2003
>
> Not having done any proper DBA work for over 10 years, but still dabbling,
> I would suggest retaining Office 2010 for it's simplicity in some areas
> where 2016 is annoyingly complex.
> Then - considering the variants of Office Avoid 2013 - 2016 etc. are
> better There are the variants of standalone 2016 and 2019 that may be on
> some client systems And then there are the online .com and subscription 365
> variants with the associated (frequently changed) install on a PC '2016'
> now dubbed 365 As well as the 64 bit versions, that are now apparently the
> default
>
> So upgrading really depends on the working environment - Did you need 64
> bit for the memory - and I have seen reports of some apps that work under
> 32 failing under 64 due to memory limits within the Access.
>
> Maybe best to try to keep the 2010 32 bit, and a 2016 32 bit proving
> environment while developing for the web based .com 365 environment with,
> maybe a server or PC based set of system maintenance apps under the
> subscription 365  but avoiding the new features.
>
> Complicated environment setup, - but the needs depend on your client/users
> environments
>
> JimB
>
> -----Original Message-----
> From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of
> fhtapia at gmail.com
> Sent: Sunday, September 15, 2019 3:18 PM
> To: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Cc: Mark Simms <mar.ko at verizon.net>; David McAfee <davidmcafee at gmail.com>
> Subject: Re: [AccessD] Windows 10 & Access 2003
>
> Thanks Mark,
>
> So should users upgrade to Access 2010? Or 2016 to avoid issues and would
> this sort of upgrade still work on an Access Database Project? (Adp)
>
> Long story long,
>
> My last place I worked at is upgrading all the user PCs to win10. When I
> left they never hired anyone to take over migrating the legacy system which
> was built on sqlserver BE and Access FE. The guys that would be able to do
> this have all raised a white flag saying they wouldn’t have the first clue
> as to how to help migrate the existing data to SAP ( a system the company
> upgraded to in 2007. ). When I worked there the work on the legacy system
> went from active to support, the project to import the data to sap went
> cold and I got tasked with other priorities since after all I was available
> to jump in and support any issues caused by os or access updates.
>
> I left the company 2 years ago, I left documentation on how to migrate and
> a fully documented database doc complete with views stored procedures and
> information on how the sqlclr was utilized and what jobs were active along
> with documentation on database triggers.
>
> I was their Sr Dba and db Developer. I also worked on their sap bi team. I
> had always wanted to get this legacy data over but never had an opportunity
> since it was never considered a priority.
>
> Thanks!
> Francisco
>
>
>
> On Fri, Sep 13, 2019 at 4:03 PM Mark Simms via AccessD <
> accessd at databaseadvisors.com> wrote:
>
> > No, but there are issues related to running AC 2007 under Win 2010.
> >
> > Mark Simms
> > marksimms at verizon.net
> > http://www.twitter.com ;@QUI_TAM_MAN
> >
> >
> > -----Original Message-----
> > From: fhtapia <fhtapia at gmail.com>
> > To: Access Developers discussion and problem solving <
> > accessd at databaseadvisors.com>
> > Sent: Thu, Sep 12, 2019 9:25 pm
> > Subject: [AccessD] Windows 10 & Access 2003
> >
> > Anybody know if there are any comparability issues running access 2003
> > on Windows 2010?
> > --
> > -Francisco <http://twitter.com/seecoolguy>
> > --
> > 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
> >
> --
> -Francisco <http://twitter.com/seecoolguy>
> --
> 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
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>