From wrwehler at gmail.com  Thu Sep 12 14:55:11 2019
From: wrwehler at gmail.com (Ryan W)
Date: Thu, 12 Sep 2019 14:55:11 -0500
Subject: [AccessD] 64-bit
Message-ID: <CAFXiSd8UGZ8WnvA3MwMDsUK9hDSK6+KuanYBKDt9EduX5Jvwmw@mail.gmail.com>

Now that Office 365/Access 2019 installs default to 64-bit, for the first
time ever has anyone spent the time to test their apps in it?

We're working on our Windows 10 rollout and are seeing even higher than
ever memory constraints with our application in 32-bit mode than ever
before.  Even thanks to John Colby's expertise in using classes to load and
unload subforms on the fly which has worked most effectively for Windows 7
running 32-bit Office/Access.

I think it's going to be time to push everyone to 64-bit versions of
Office, even if we aren't on the O365 suite.

From fhtapia at gmail.com  Thu Sep 12 20:24:02 2019
From: fhtapia at gmail.com (fhtapia at gmail.com)
Date: Thu, 12 Sep 2019 18:24:02 -0700
Subject: [AccessD] Windows 10 & Access 2003
Message-ID: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>

Anybody know if there are any comparability issues running access 2003 on
Windows 2010?
-- 
-Francisco <http://twitter.com/seecoolguy>

From charlotte.foust at gmail.com  Fri Sep 13 01:25:06 2019
From: charlotte.foust at gmail.com (Charlotte Foust)
Date: Thu, 12 Sep 2019 23:25:06 -0700
Subject: [AccessD] 64-bit
In-Reply-To: <CAFXiSd8UGZ8WnvA3MwMDsUK9hDSK6+KuanYBKDt9EduX5Jvwmw@mail.gmail.com>
References: <CAFXiSd8UGZ8WnvA3MwMDsUK9hDSK6+KuanYBKDt9EduX5Jvwmw@mail.gmail.com>
Message-ID: <CAH+Met8+5kpZhc+BV9A00HkPN9uPMquurjib+ppi9+_aFkC1KA@mail.gmail.com>

We ran into issues because our Access 2010 application is 32 bit.  It would
not run when opened on a machine with 64 bit Office 365 installed because
it was looking for the 64 bit Oulook driver to send an email


On Thu, Sep 12, 2019, 12:57 PM Ryan W <wrwehler at gmail.com> wrote:

> Now that Office 365/Access 2019 installs default to 64-bit, for the first
> time ever has anyone spent the time to test their apps in it?
>
> We're working on our Windows 10 rollout and are seeing even higher than
> ever memory constraints with our application in 32-bit mode than ever
> before.  Even thanks to John Colby's expertise in using classes to load and
> unload subforms on the fly which has worked most effectively for Windows 7
> running 32-bit Office/Access.
>
> I think it's going to be time to push everyone to 64-bit versions of
> Office, even if we aren't on the O365 suite.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From jackandpat.d at gmail.com  Fri Sep 13 06:19:51 2019
From: jackandpat.d at gmail.com (jack drawbridge)
Date: Fri, 13 Sep 2019 07:19:51 -0400
Subject: [AccessD] 64-bit
In-Reply-To: <CAH+Met8+5kpZhc+BV9A00HkPN9uPMquurjib+ppi9+_aFkC1KA@mail.gmail.com>
References: <CAFXiSd8UGZ8WnvA3MwMDsUK9hDSK6+KuanYBKDt9EduX5Jvwmw@mail.gmail.com>
	<CAH+Met8+5kpZhc+BV9A00HkPN9uPMquurjib+ppi9+_aFkC1KA@mail.gmail.com>
Message-ID: <CAKvidAtCqwwGMmGir7va5CTzmJHnDi+z0PkX=bAVQjZd8ZbJaQ@mail.gmail.com>

Ryan,
I do not have direct experience with moving from 32 to 64bit Access.
 Here is a  link to Daniel Pineault's site
<https://www.devhut.net/2017/04/13/access-x32-vs-x64-compatibility/>  that
has some observations that may be useful to you.

Good luck,

Jack

On Fri, Sep 13, 2019 at 2:25 AM Charlotte Foust <charlotte.foust at gmail.com>
wrote:

> We ran into issues because our Access 2010 application is 32 bit.  It would
> not run when opened on a machine with 64 bit Office 365 installed because
> it was looking for the 64 bit Oulook driver to send an email
>
>
> On Thu, Sep 12, 2019, 12:57 PM Ryan W <wrwehler at gmail.com> wrote:
>
> > Now that Office 365/Access 2019 installs default to 64-bit, for the first
> > time ever has anyone spent the time to test their apps in it?
> >
> > We're working on our Windows 10 rollout and are seeing even higher than
> > ever memory constraints with our application in 32-bit mode than ever
> > before.  Even thanks to John Colby's expertise in using classes to load
> and
> > unload subforms on the fly which has worked most effectively for Windows
> 7
> > running 32-bit Office/Access.
> >
> > I think it's going to be time to push everyone to 64-bit versions of
> > Office, even if we aren't on the O365 suite.
> > --
> > 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
>

From jimdettman at verizon.net  Fri Sep 13 06:44:35 2019
From: jimdettman at verizon.net (Jim Dettman)
Date: Fri, 13 Sep 2019 07:44:35 -0400
Subject: [AccessD] 64-bit
In-Reply-To: <CAFXiSd8UGZ8WnvA3MwMDsUK9hDSK6+KuanYBKDt9EduX5Jvwmw@mail.gmail.com>
References: <CAFXiSd8UGZ8WnvA3MwMDsUK9hDSK6+KuanYBKDt9EduX5Jvwmw@mail.gmail.com>
Message-ID: <04b401d56a28$9e5ed9b0$db1c8d10$@verizon.net>

<< I think it's going to be time to push everyone to 64-bit versions of
Office, even if we aren't on the O365 suite.>>

 I would say that would be a wise move at this point.

 Microsoft is starting to push 64 bit because as you have found, later
versions of Office are starting to run out of process address space.   I
don't believe they plan on making Access Large Address aware, so the only
"fix" for this is to move to 64 bit.

 When you move to 64 bit, all your API calls, calls to .DLL's or .OCX's, and
ODBC drivers all must be 64 bit.  Apps without any of those will just run.
Apps with those will need some porting. If you haven't dived into 64 bit as
yet, you should read the following:

Compatibility Between the 32-bit and 64-bit Versions of Office 2010
http://msdn.microsoft.com/en-us/library/ee691831(office.14).aspx

 Read the section "Introducing the VBA 7 Code Base" carefully.   It's
confusing at best.    The thing to keep clear is that the WIN64 compiler
constant is telling you if *Office* is running in 64 bit or not and VBA7 is
if you are working in the version of VBA that supports the PtrSafe Keyword
and LongLong data type (Access 2010 and above).

 There are all the API calls that will need to be modified for 64 bit:

http://www.microsoft.com/download/en/confirmation.aspx?displaylang=en&id=997
0

and here's a list of all the calls that were modified for 64 bit:
http://msdn.microsoft.com/en-us/library/aa383663(VS.85).aspx

 .DLLs, OCX's, etc you need to check with the vendor's.

ODBC drivers almost always come with 32 and 64 bit versions now, so that's
not as much of an issue as it once was.

 Only other comment is that when working with ODBC and DSN's,  you must use
the appropriate ODBC applet.  32 bit version is
C:\Windows\SysWoW64\Odbcad32.exe   and the 64 bit version is
C:\Windows\System32\Odbcad32.exe      And that executable in both cases is
correct...it is the same name.   Also to avoid confusion, make sure you
suffix any DSN's with _32 or _64.   The two applets depending on the type of
DSN (File, System, or User) may display both 32 and 64 bit setups.  This was
required for backwards compatibility, but it makes it very confusing at
times what you're working with if you don't use suffixes.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Ryan W
Sent: Thursday, September 12, 2019 3:55 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] 64-bit

Now that Office 365/Access 2019 installs default to 64-bit, for the first
time ever has anyone spent the time to test their apps in it?

We're working on our Windows 10 rollout and are seeing even higher than
ever memory constraints with our application in 32-bit mode than ever
before.  Even thanks to John Colby's expertise in using classes to load and
unload subforms on the fly which has worked most effectively for Windows 7
running 32-bit Office/Access.

I think it's going to be time to push everyone to 64-bit versions of
Office, even if we aren't on the O365 suite.
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


From wrwehler at gmail.com  Fri Sep 13 06:56:23 2019
From: wrwehler at gmail.com (Ryan W)
Date: Fri, 13 Sep 2019 06:56:23 -0500
Subject: [AccessD] 64-bit
In-Reply-To: <04b401d56a28$9e5ed9b0$db1c8d10$@verizon.net>
References: <CAFXiSd8UGZ8WnvA3MwMDsUK9hDSK6+KuanYBKDt9EduX5Jvwmw@mail.gmail.com>
	<04b401d56a28$9e5ed9b0$db1c8d10$@verizon.net>
Message-ID: <B6536793-B5AE-4A17-8EDF-94CFD4344605@gmail.com>

Thanks. I had already gone through and made the necessarily changes previously for 64-bit compiling with the compiler constant if/then/else logic and seemed to get a clean compile. I guess rigorous testing is next. 



Sent from my iPhone

> On Sep 13, 2019, at 6:44 AM, Jim Dettman via AccessD <accessd at databaseadvisors.com> wrote:
> 
> << I think it's going to be time to push everyone to 64-bit versions of
> Office, even if we aren't on the O365 suite.>>
> 
> I would say that would be a wise move at this point.
> 
> Microsoft is starting to push 64 bit because as you have found, later
> versions of Office are starting to run out of process address space.   I
> don't believe they plan on making Access Large Address aware, so the only
> "fix" for this is to move to 64 bit.
> 
> When you move to 64 bit, all your API calls, calls to .DLL's or .OCX's, and
> ODBC drivers all must be 64 bit.  Apps without any of those will just run.
> Apps with those will need some porting. If you haven't dived into 64 bit as
> yet, you should read the following:
> 
> Compatibility Between the 32-bit and 64-bit Versions of Office 2010
> http://msdn.microsoft.com/en-us/library/ee691831(office.14).aspx
> 
> Read the section "Introducing the VBA 7 Code Base" carefully.   It's
> confusing at best.    The thing to keep clear is that the WIN64 compiler
> constant is telling you if *Office* is running in 64 bit or not and VBA7 is
> if you are working in the version of VBA that supports the PtrSafe Keyword
> and LongLong data type (Access 2010 and above).
> 
> There are all the API calls that will need to be modified for 64 bit:
> 
> http://www.microsoft.com/download/en/confirmation.aspx?displaylang=en&id=997
> 0
> 
> and here's a list of all the calls that were modified for 64 bit:
> http://msdn.microsoft.com/en-us/library/aa383663(VS.85).aspx
> 
> .DLLs, OCX's, etc you need to check with the vendor's.
> 
> ODBC drivers almost always come with 32 and 64 bit versions now, so that's
> not as much of an issue as it once was.
> 
> Only other comment is that when working with ODBC and DSN's,  you must use
> the appropriate ODBC applet.  32 bit version is
> C:\Windows\SysWoW64\Odbcad32.exe   and the 64 bit version is
> C:\Windows\System32\Odbcad32.exe      And that executable in both cases is
> correct...it is the same name.   Also to avoid confusion, make sure you
> suffix any DSN's with _32 or _64.   The two applets depending on the type of
> DSN (File, System, or User) may display both 32 and 64 bit setups.  This was
> required for backwards compatibility, but it makes it very confusing at
> times what you're working with if you don't use suffixes.
> 
> Jim.
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Ryan W
> Sent: Thursday, September 12, 2019 3:55 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] 64-bit
> 
> Now that Office 365/Access 2019 installs default to 64-bit, for the first
> time ever has anyone spent the time to test their apps in it?
> 
> We're working on our Windows 10 rollout and are seeing even higher than
> ever memory constraints with our application in 32-bit mode than ever
> before.  Even thanks to John Colby's expertise in using classes to load and
> unload subforms on the fly which has worked most effectively for Windows 7
> running 32-bit Office/Access.
> 
> I think it's going to be time to push everyone to 64-bit versions of
> Office, even if we aren't on the O365 suite.
> -- 
> 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


From mar.ko at verizon.net  Fri Sep 13 18:00:40 2019
From: mar.ko at verizon.net (Mark Simms)
Date: Fri, 13 Sep 2019 23:00:40 +0000 (UTC)
Subject: [AccessD] 64-bit
In-Reply-To: <04b401d56a28$9e5ed9b0$db1c8d10$@verizon.net>
References: <CAFXiSd8UGZ8WnvA3MwMDsUK9hDSK6+KuanYBKDt9EduX5Jvwmw@mail.gmail.com>
	<04b401d56a28$9e5ed9b0$db1c8d10$@verizon.net>
Message-ID: <141099180.7218647.1568415640784@mail.yahoo.com>

Well said Jim.....a move to 64 bit can require a lot of work !

Mark Simms
marksimms at verizon.net
http://www.twitter.com?;@QUI_TAM_MAN


-----Original Message-----
From: Jim Dettman via AccessD <accessd at databaseadvisors.com>
To: 'Access Developers discussion and problem solving' <accessd at databaseadvisors.com>
Cc: Jim Dettman <jimdettman at verizon.net>
Sent: Fri, Sep 13, 2019 7:45 am
Subject: Re: [AccessD] 64-bit

<< I think it's going to be time to push everyone to 64-bit versions of
Office, even if we aren't on the O365 suite.>>

 I would say that would be a wise move at this point.

 Microsoft is starting to push 64 bit because as you have found, later
versions of Office are starting to run out of process address space.? I
don't believe they plan on making Access Large Address aware, so the only
"fix" for this is to move to 64 bit.

 When you move to 64 bit, all your API calls, calls to .DLL's or .OCX's, and
ODBC drivers all must be 64 bit.? Apps without any of those will just run.
Apps with those will need some porting. If you haven't dived into 64 bit as
yet, you should read the following:

Compatibility Between the 32-bit and 64-bit Versions of Office 2010
http://msdn.microsoft.com/en-us/library/ee691831(office.14).aspx

 Read the section "Introducing the VBA 7 Code Base" carefully.? It's
confusing at best.? ? The thing to keep clear is that the WIN64 compiler
constant is telling you if *Office* is running in 64 bit or not and VBA7 is
if you are working in the version of VBA that supports the PtrSafe Keyword
and LongLong data type (Access 2010 and above).

 There are all the API calls that will need to be modified for 64 bit:

http://www.microsoft.com/download/en/confirmation.aspx?displaylang=en&id=997
0

and here's a list of all the calls that were modified for 64 bit:
http://msdn.microsoft.com/en-us/library/aa383663(VS.85).aspx

 .DLLs, OCX's, etc you need to check with the vendor's.

ODBC drivers almost always come with 32 and 64 bit versions now, so that's
not as much of an issue as it once was.

 Only other comment is that when working with ODBC and DSN's,? you must use
the appropriate ODBC applet.? 32 bit version is
C:\Windows\SysWoW64\Odbcad32.exe? and the 64 bit version is
C:\Windows\System32\Odbcad32.exe? ? ? And that executable in both cases is
correct...it is the same name.? Also to avoid confusion, make sure you
suffix any DSN's with _32 or _64.? The two applets depending on the type of
DSN (File, System, or User) may display both 32 and 64 bit setups.? This was
required for backwards compatibility, but it makes it very confusing at
times what you're working with if you don't use suffixes.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Ryan W
Sent: Thursday, September 12, 2019 3:55 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] 64-bit

Now that Office 365/Access 2019 installs default to 64-bit, for the first
time ever has anyone spent the time to test their apps in it?

We're working on our Windows 10 rollout and are seeing even higher than
ever memory constraints with our application in 32-bit mode than ever
before.? Even thanks to John Colby's expertise in using classes to load and
unload subforms on the fly which has worked most effectively for Windows 7
running 32-bit Office/Access.

I think it's going to be time to push everyone to 64-bit versions of
Office, even if we aren't on the O365 suite.
-- 
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

From mar.ko at verizon.net  Fri Sep 13 18:02:36 2019
From: mar.ko at verizon.net (Mark Simms)
Date: Fri, 13 Sep 2019 23:02:36 +0000 (UTC)
Subject: [AccessD] Windows 10 & Access 2003
In-Reply-To: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>
References: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>
Message-ID: <259104230.7184359.1568415756588@mail.yahoo.com>

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

From fhtapia at gmail.com  Sun Sep 15 09:18:02 2019
From: fhtapia at gmail.com (fhtapia at gmail.com)
Date: Sun, 15 Sep 2019 07:18:02 -0700
Subject: [AccessD] Windows 10 & Access 2003
In-Reply-To: <259104230.7184359.1568415756588@mail.yahoo.com>
References: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>
	<259104230.7184359.1568415756588@mail.yahoo.com>
Message-ID: <CAP+kXmbwkfgCcBQV4+jaRfqq3z-YtjN8yNY4eE7ZZnB67XhgZA@mail.gmail.com>

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>

From jamesbutton at blueyonder.co.uk  Sun Sep 15 09:47:41 2019
From: jamesbutton at blueyonder.co.uk (James Button)
Date: Sun, 15 Sep 2019 15:47:41 +0100
Subject: [AccessD] Windows 10 & Access 2003
In-Reply-To: <CAP+kXmbwkfgCcBQV4+jaRfqq3z-YtjN8yNY4eE7ZZnB67XhgZA@mail.gmail.com>
References: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>	<259104230.7184359.1568415756588@mail.yahoo.com>
	<CAP+kXmbwkfgCcBQV4+jaRfqq3z-YtjN8yNY4eE7ZZnB67XhgZA@mail.gmail.com>
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAO8VDlNCBfdEkctCy61lm0HCgAAAEAAAAGgTOISqi61NmcjOZIZD0cQBAAAAAA==@blueyonder.co.uk>

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



From rockysmolin at bchacc.com  Sun Sep 15 13:13:53 2019
From: rockysmolin at bchacc.com (Rocky Smolin)
Date: Sun, 15 Sep 2019 11:13:53 -0700
Subject: [AccessD] Windows 10 & Access 2003
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAO8VDlNCBfdEkctCy61lm0HCgAAAEAAAAGgTOISqi61NmcjOZIZD0cQBAAAAAA==@blueyonder.co.uk>
References: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>	<259104230.7184359.1568415756588@mail.yahoo.com>	<CAP+kXmbwkfgCcBQV4+jaRfqq3z-YtjN8yNY4eE7ZZnB67XhgZA@mail.gmail.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAO8VDlNCBfdEkctCy61lm0HCgAAAEAAAAGgTOISqi61NmcjOZIZD0cQBAAAAAA==@blueyonder.co.uk>
Message-ID: <002701d56bf1$54eee390$feccaab0$@bchacc.com>

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



From fhtapia at gmail.com  Mon Sep 16 08:15:04 2019
From: fhtapia at gmail.com (fhtapia at gmail.com)
Date: Mon, 16 Sep 2019 06:15:04 -0700
Subject: [AccessD] Windows 10 & Access 2003
In-Reply-To: <002701d56bf1$54eee390$feccaab0$@bchacc.com>
References: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>
	<259104230.7184359.1568415756588@mail.yahoo.com>
	<CAP+kXmbwkfgCcBQV4+jaRfqq3z-YtjN8yNY4eE7ZZnB67XhgZA@mail.gmail.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAO8VDlNCBfdEkctCy61lm0HCgAAAEAAAAGgTOISqi61NmcjOZIZD0cQBAAAAAA==@blueyonder.co.uk>
	<002701d56bf1$54eee390$feccaab0$@bchacc.com>
Message-ID: <CAP+kXma49UfWfqeyB-jWFFpwfkzZCzzAdZW6wAv9k=i94CZF8w@mail.gmail.com>

Thank you all! It sounds like 2010 should work.



On Sun, Sep 15, 2019 at 11:14 AM Rocky Smolin <rockysmolin at bchacc.com>
wrote:

> 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
>
-- 
-Francisco <http://twitter.com/seecoolguy>

From jbartow at winhaven.net  Tue Sep 17 13:38:31 2019
From: jbartow at winhaven.net (John Bartow)
Date: Tue, 17 Sep 2019 18:38:31 +0000
Subject: [AccessD] Windows 10 & Access 2003
In-Reply-To: <002701d56bf1$54eee390$feccaab0$@bchacc.com>
References: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>
	<259104230.7184359.1568415756588@mail.yahoo.com>
	<CAP+kXmbwkfgCcBQV4+jaRfqq3z-YtjN8yNY4eE7ZZnB67XhgZA@mail.gmail.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAO8VDlNCBfdEkctCy61lm0HCgAAAEAAAAGgTOISqi61NmcjOZIZD0cQBAAAAAA==@blueyonder.co.uk>
	<002701d56bf1$54eee390$feccaab0$@bchacc.com>
Message-ID: <BL0PR11MB3153E72F1A51F4051C2458A6D88F0@BL0PR11MB3153.namprd11.prod.outlook.com>

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


From davidmcafee at gmail.com  Tue Sep 17 14:27:43 2019
From: davidmcafee at gmail.com (David McAfee)
Date: Tue, 17 Sep 2019 12:27:43 -0700
Subject: [AccessD] Windows 10 & Access 2003
In-Reply-To: <BL0PR11MB3153E72F1A51F4051C2458A6D88F0@BL0PR11MB3153.namprd11.prod.outlook.com>
References: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>
	<259104230.7184359.1568415756588@mail.yahoo.com>
	<CAP+kXmbwkfgCcBQV4+jaRfqq3z-YtjN8yNY4eE7ZZnB67XhgZA@mail.gmail.com>
	<!&!AAAAAAAAAAAYAAAAAAAAAO8VDlNCBfdEkctCy61lm0HCgAAAEAAAAGgTOISqi61NmcjOZIZD0cQBAAAAAA==@blueyonder.co.uk>
	<002701d56bf1$54eee390$feccaab0$@bchacc.com>
	<BL0PR11MB3153E72F1A51F4051C2458A6D88F0@BL0PR11MB3153.namprd11.prod.outlook.com>
Message-ID: <CAMhYZWZF5uU5d++vbOp5nwRHuO6CZQtUSkJrVa+jRLOWk8M4SA@mail.gmail.com>

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
>

From jimdettman at verizon.net  Tue Sep 17 14:37:52 2019
From: jimdettman at verizon.net (Jim Dettman)
Date: Tue, 17 Sep 2019 15:37:52 -0400
Subject: [AccessD] Windows 10 & Access 2003
In-Reply-To: <CAMhYZWZF5uU5d++vbOp5nwRHuO6CZQtUSkJrVa+jRLOWk8M4SA@mail.gmail.com>
References: <CAP+kXmabziBNEn1V9j_fgV7PDPnt-gtwzY+ufE=G=vc0ppX11w@mail.gmail.com>	<259104230.7184359.1568415756588@mail.yahoo.com>	<CAP+kXmbwkfgCcBQV4+jaRfqq3z-YtjN8yNY4eE7ZZnB67XhgZA@mail.gmail.com>	<!&!AAAAAAAAAAAYAAAAAAAAAO8VDlNCBfdEkctCy61lm0HCgAAAEAAAAGgTOISqi61NmcjOZIZD0cQBAAAAAA==@blueyonder.co.uk>	<002701d56bf1$54eee390$feccaab0$@bchacc.com>	<BL0PR11MB3153E72F1A51F4051C2458A6D88F0@BL0PR11MB3153.namprd11.prod.outlook.com>
	<CAMhYZWZF5uU5d++vbOp5nwRHuO6CZQtUSkJrVa+jRLOWk8M4SA@mail.gmail.com>
Message-ID: <001a01d56d8f$66037070$320a5150$@verizon.net>


Actually, it was 2013:

https://support.office.com/en-us/article/discontinued-features-and-modified-functionality-in-access-2013-bc006fc3-5b48-499e-8c7d-9a2dfef68e2f

 A2010 was the last "full" version of Access that we were all used to for so many years.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David McAfee
Sent: Tuesday, September 17, 2019 3:28 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Windows 10 & Access 2003

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
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com