[AccessD] Back from SQL Server

[Stuart McLachlan]

Yep, I've run into it a few times with old systems when run on new machines with a recent 
64bit Office installed.

Sounds like the FE was built in the days of 32bit Office with standard WIn32 API function 
declarations,  all machines other than the laptop are using 32 bit Office installations and the 
laptop is using 64bit Office.

You really should update the front end to make all API declarations compatible with both 
32bit and 64bit Office by using PTRSAFE and LONGPTR where appropriate.

On 18 Mar 2022 at 17:34, accesspro at cox.net wrote:

> 
> 
> My project to rid an old app of SQL Server is going well.
> Thanks for all who responded.
> Once I had all local tables, the Access file compacted without a
> problem and runs fine. Which was the objective. I just need to get him
> to back up. An odd issue cropped up when testing. When run on his
> desktop and on my home machine, starts right up. When run on the
> laptop, I get the following error message: Compile error:
> 
> The code in this project must be updated for use on 64-bit
> systems. Please review and update Declare statements and then
> mark them with the PtrSafe attribute.
> 
> The solution seems to be pretty simple. But it is weird that I receive
> this only on the laptop. All three machines are Win 10 64 bit. All are
> using Off 365. Has anyone run into this? I would rather not fiddle w
> the code..
> 
> TIA
> Bob
> 
> 
> 
> 
> 
> -----------
> No
> Not cost. Just simplicity. I anticipate running all of it on a single
> laptop. I will ultimately gut a lot of the functionality.
> 
> thx
> 
> Bob
> 
> 
> -----Original Message-----
> From: AccessD <accessd-bounces+accesspro=cox.net at databaseadvisors.com>
> On Behalf Of Paul Hartland via AccessD Sent: Sunday, March 6, 2022
> 8:14 PM To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com> Cc: Paul Hartland
> <paul.hartland at googlemail.com> Subject: Re: [AccessD] Back from SQL
> Server
> 
> Is it cost driving the decision back to access, can they not go to SQL
> Server Exoress ?
> 
> On Mon, 7 Mar 2022, 04:10 Stuart McLachlan, <stuart at lexacorp.com.pg>
> wrote:
> 
> > What sort of connection to the SQL Server (what driver?)
> >
> >
> > On 6 Mar 2022 at 19:46, accesspro at cox.net wrote:
> >
> > > Hello to the list,
> > >
> > > A long time ago I did a pretty complex Access app.
> > > The client went on later to have someone hook it up to SQL Server.
> > > They now are scaling their biz back and wish to just use Access. I
> > > bet there is a way to "import" the tables back into Access, but I
> > > don't know how. Not too concerned about any views yet.
> > >
> > > TIA
> > > Bob Heygood
> --
> 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
>