Access to the database in a 64-bit XP operating system

I just bought a new 64-bit machine and installed a 64-bit XP to try it out.
As a result, there are many problems along the way. First, the installation disk cannot be started by itself. I don't know what Microsoft is doing? The VlP version of the DVD contains multiple versions of XP, but only 32-bit can be installed on its own, 64-bit edition needs to first engrave the ISO file into a CD, and then install dizzy, fortunately, I read the instruction file first .)

Then, the right-click menu cannot be properly registered by ultraedit and WinRAR, and the windows rogue software cleaner cannot work normally.

Next, the serial number of vs2005 is not automatically filled in. I don't know why. It is automatically filled when installed on 32-bit machines.

The most depressing thing is: Use vs2005 to create a project and connect to a database created in Access 2003. During runtime, the Microsoft. Jet. oledb.4.0 database is directly generated during fill data.ProgramNo registration error.

Invalidoperationexception
The 'Microsoft. Jet. oledb.4.0 'provider is not registered on the local machine.

After multiple checks, it seems that the data engine has been well registered. There is no result for inquiring around. That depressing thing ............

Finally, I learned through some official channels that it was originally a compatibility issue of the Microsoft Jet Data Engine. The solution is to compile the program into a 32-bit version.

Modification method:
Open the Configuration Manager and change platform to x86. For example:

Re-compile and run. I just bought a new 64-bit machine and installed a 64-bit XP to try it out.
As a result, there are many problems along the way. First, the installation disk cannot be started by itself. I don't know what Microsoft is doing? The VlP version of the DVD contains multiple versions of XP, but only 32-bit can be installed on its own, 64-bit edition needs to first engrave the ISO file into a CD, and then install dizzy, fortunately, I read the instruction file first .)

Then, the right-click menu cannot be properly registered by ultraedit and WinRAR, and the windows rogue software cleaner cannot work normally.

Next, the serial number of vs2005 is not automatically filled in. I don't know why. It is automatically filled when installed on 32-bit machines.

The most depressing thing is: Use vs2005 to create a project and connect to a database created in Access 2003. During runtime, the Microsoft. Jet. oledb.4.0 database provider is not registered during fill data.

Invalidoperationexception
The 'Microsoft. Jet. oledb.4.0 'provider is not registered on the local machine.

After multiple checks, it seems that the data engine has been well registered. There is no result for inquiring around. That depressing thing ............

Finally, I learned through some official channels that it was originally a compatibility issue of the Microsoft Jet Data Engine. The solution is to compile the program into a 32-bit version.

Modification method:
Open the Configuration Manager and change platform to x86. For example:

Re-compile and run.