[AccessD] Upsizing ACCDB to SQL Server

[Arthur Fuller]

In all my many years of Access development, I don't recall ever using the
DECLARE statement, so please forgive my ignorance It would appear that it's
fpr developers that must maintain versions of an app's code that depend on
such things as 32 or 64 bit. Is that correct?  Is that all there is to it?
Am I missing something? Couldn't that be done with compiler directives?
Please advise. I am not trying to start a war here, just trying to learn..

Following up on something Stuart wrote, and given an app of
reasonably large size, is there some simple way to find all API calls, so I
can isolate them and deal with them prior to trying to migrate a 32 bit FE
to a 64 bit equivalent?
Perhaps there is  a more fundamental question here: what does one gain by
migrating? Performance, capacity (meaning larger data sizes of types and
tables and databases), arithmetic accuracy in binary/decimal conversions?
I'm just guessing here, I really have no idea  Please explain or link me to
an explanation of why it is worth the  effort to convert from 32 to 64 bit.
what are the gains? Fortunately I don't have to worry about dealing with
apps that must support both. Currently everything exists in 32 bit
installations, and it's a small task to convert them all to 64 bit, since
there are only a few computers on a single network, so my situation does
not compare to that of developers who must support multiple versions of the
same software (whew!),

But I still don't really get what is gained by switching. Could someone
kindly explain this to me?


Second, is there some quick way of finding all the calls to WinAPIs that I
must take care of before or after migrating? Rick Fisher's superb Find and
Replace is in my toolkit. Is that sufficient to identify all the
occurrences that need examination/elimination/revision?

I'm in one of those rare situations where it's the client who wants to move
to something new (64 bit) and I am the reluctant one, wondering why. So
somebody please tell me what the app will gain by this move.

On Tue, Oct 19, 2021 at 5:22 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> We've discussed PtrSafe and when and how to use it here many times -
> including in threads
> you started.  (I've got 104 messages in my AccessD mail folder that
> mention it)
>
> Last September, you seemed to know a bit about it when you said:
>
> "I develop in 2010. I keep things simple so I don't run into problems with
> folks who use later versions.  The only problem I've had is with those who
> use 64-bit access and that is worked around with PtrSafe. "
>
> :)
>
>
> On 19 Oct 2021 at 7:48, Rocky Smolin wrote:
>
> > Isn't there also something that you have to do with SafePtr?
> >
> > Rocky
> >
> >
> > On Tue, Oct 19, 2021 at 4:39 AM Jim Dettman via AccessD <
> > accessd at databaseadvisors.com> wrote:
> >
> > > Arthur,
> > >
> > > 1.  SQL Server Migration Assistant:
> > >
> > >
> > > https://docs.microsoft.com/en-us/sql/ssma/sql-server-migration-assis
> > > tant?vie w=sql-server-ver15
> > > <https://docs.microsoft.com/en-us/sql/ssma/sql-server-migration-assi
> > > stant?view=sql-server-ver15>
> > >
> > > 2. Any Win API calls will need to be updated.    Also any external
> > > libs, .OCX's, Active-x controls, etc.   all need to be 64 bit.   Can
> > > give you more detail on that if you need it.    But if it's all
> > > native Access, then you just switch and a recompile is all that is
> > > required if you are distributing apps as .accde's.  If it's an
> > > .accdb, it will re-compile on the fly.
> > >
> > >   Note that from Office 2013 and up, you cannot mix and match 32 bit
> > >   and 64
> > > on the same machine.  It all has to be one or the other.
> > >
> > > Jim.
> > >
> > > -----Original Message-----
> > > From: AccessD On Behalf Of Arthur Fuller
> > > Sent: Tuesday, October 19, 2021 7:28 AM
> > > To: Access Developers discussion and problem solving
> > > <accessd at databaseadvisors.com>
> > > Subject: [AccessD] Upsizing ACCDB to SQL Server
> > >
> > > This is actually two related questions:
> > > 1. What is the recommended way to upsize an Access ACCDB to SQL
> > > Server? 2. The client also wants me to move the app from 32 bit to
> > > 64 bit, What potential problems am I looking at?
> > >
> > > Thanks.
> > >
> > > --
> > > Arthur
> > > --
> > > 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
>


-- 
Arthur