How to do? So, more than the emergency ah,,,

CodePudding user response:

Oh, can't, no one back,,
Don't have a 64 - bit development

CodePudding user response:

You've installed sp1?

CodePudding user response:

The solution?

CodePudding user response:

Used 64, 32 is not yet understood

CodePudding user response:

LZ is solved?

CodePudding user response:

What you need to run under the bad border, in the compiler under the environment, the generated exe
Generated exe in different environment, you will, of course, out of the question

CodePudding user response:

1. Download operation AccessDatabaseEngine_x64. Exe

(http://www.microsoft.com/downloads/en/details.aspx? FamilyID=c06b8369-60 b64 dd - 4 - a44b - 84 b371ede16d & amp; Displaylang=en)


2. Change the connection string:

Driver={Microsoft Access Driver (*. MDB, *. Accdb)}; DBQ=MDB. MDB; Uid=admin; The PWD=password;

I use this method test success, ha ha, spent two days time, search ability or not...

CodePudding user response:

Windows 7 32 sp1, xp sp3. 32 vb6 their compilation can only run on the same system, Windows 7 compilation on out of the 430 xp ado new you mistake, can use createObject normal,,,,,,,,,,,,,,,,,

Now compromise is XP, Windows 7, and their respective compiled a ~ ~ ~

Mdac2.8 mdactyp. Exe when installation prompt version are not compatible
Try the scenario, the upstairs,,,

CodePudding user response:

The question is a question of _WIN32_WINNT value? Or other macro?
I am now in development under the Windows server 2003, how?

CodePudding user response:

Problem solved

CodePudding user response:

I 32 to 64 is settled, and around is definitely no corresponding ADO version installed and registered

CodePudding user response:

In a 64 - bit Windows:
64 exe and DLL in the directory c: \ Windows \ sys tem32 directory.
32 bit exe and DLL in the directory c: \ Windows \ sys wow64 directory.