A bit of a year of procedures, development tools vs2005 + access, packaging, after the release under xp and Windows 7 is fine;
Two days before, the system upgrade to win10, found that the program can run normally, but read access point problems, performance is as follows:
1 keep a record, can modify the table used to record the same column of data;
2 read read all data to 0;
But to open and close the data connection is no problem, data connection with SetConnectionString="Microsoft. Jet. The OLEDB. 4.0";

Win10 64 - bit system installation is home edition + office2016,
With office2003 winxp 32 bit system;
Windows 7 64 - bit is not installed office;
Don't know if there is any problem encountered the problem of the great god, please give advice, thank you first.

CodePudding user response:

Is generally ado package version are not compatible, or every time you compile under xp ado package contains into, that whether Windows 7 win10, is no problem

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.
So pay attention to:
In win64 system registered under 32-bit ocx DLL to 32 ocx or copy the DLL to the c: \ Windows \ syswow64 \ directory,
And registered to c: \ Windows \ syswow64 \ regsvr32 XXXXXXX ocx or DLL
Under win64 a system set up 32-bit programs use a database alias to c: \ Windows \ \ syswow64 \ cliconfg exe
Under win64 a system set up a 32-bit application system DSN to c: \ Windows \ \ syswow64 \ odbcad32 exe
A 64 - bit Windows platform attention point of the file system redirection http://www.cnblogs.com/jiake/p/4981555.html
64 - bit Windows platforms attention point of the registry to redirect http://www.cnblogs.com/jiake/p/4956218.html

CodePudding user response:

Drive problem, create a new text document, extension udl instead, look at the drive

CodePudding user response:

How do you read? Haven't seen this kind of thing can be your SQL directly in the access to see