The code in this project must be updated for use on 64-bit systems.

[Falcon88]

Hi all dears

Please help me to run this app. On my machine
64bit system

I need it necessarily.

 

[tvanstiphout]

This may help:

Download Office 2010 Help Files: Win32API_PtrSafe with 64-bit Support from Official Microsoft Download Center

Windows API Declarations and Constants for Visual Basic (Updated for the 64-bit version of Microsoft Office 2010) provides declarations for Microsoft Visual Basic programmers who want to call Windows API routines. This file is updated to include calls to the 64-bit version of Microsoft Office 2010.

www.microsoft.com

 

[Gasman]

Hi all dears

Please help me to run this app. On my machine
64bit system

I need it necessarily.

If you do not really need 64bit, then uninstall and install 32bit, at least for now, while you work out what needs to be changed.

 

[Falcon88]

If you do not really need 64bit, then uninstall and install 32bit, at least for now, while you work out what needs to be changed.

I do as in this replay

Microsoft Visual Basic for Applications Compile error: The code in this project must be updated for use on 64-bit systems.

Good day all, Microsoft Visual Basic for Applications 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. I have been running MS Office Professional 2010 on Windows 7...

www.access-programmers.co.uk

But the code do not work still gives me error

U can download database_comparetool1

To see where the error

 

[Gasman]

I do not have 64 bit, nor know what needs to be changed, well more or less.
I am just suggesting a quick way to get your dB working again.

Have you bothered to look at the link in post #2 ?

 

[GPGeorge]

I do as in this replay

Microsoft Visual Basic for Applications Compile error: The code in this project must be updated for use on 64-bit systems.

Good day all, Microsoft Visual Basic for Applications 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. I have been running MS Office Professional 2010 on Windows 7...

www.access-programmers.co.uk

But the code do not work still gives me error

U can download database_comparetool1

To see where the error

You can

I do as in this replay

Microsoft Visual Basic for Applications Compile error: The code in this project must be updated for use on 64-bit systems.

Good day all, Microsoft Visual Basic for Applications 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. I have been running MS Office Professional 2010 on Windows 7...

www.access-programmers.co.uk

But the code do not work still gives me error

U can download database_comparetool1

To see where the error

Show us your API Declare code after you revised it.

 

[Pat Hartman]

To say it in plain English. You cannot run an .accde created with a 64-bit version of Access on a system with 32-bit Access installed or vice versa. You need to either convert the .accde to the version you have installed OR uninstall what you have and install a compatible version. That's it! Two options. If you don't have the source for the .accde then you're down to ONE option and that is make your installed version match the version of the .accde.

 

[Gasman]

My thoughts were it was the other way?
32bit db on a new 64bit access system.

 

[Pat Hartman]

It doesn't matter which way for .accde's. They only run on the bit version that created them. You can't run a 64 bit .accde with Access 32 bit and you can't run a 32 bit .accde with Access 64 bit. Period. You have more flexibility with .accdb's. You can run either on either PROVIDED you include a code check that uses 64 bit code when running with 64 bit Access and 32 bit code when running with 32 bit Access.

 

[Gasman]

It is even an mdb file?
You might get away from conditional compiling, but just adding ptrsafe on it's own, is not going to cut it.