The original design of 32 bit systems under open the excel spreadsheet, to a 64 - bit system will make a mistake, please help advice, thank you.

CodePudding user response:

System problems,
I recently wrote a program that will use Excel spreadsheets:
Use Excel COM object operation form, which is used to read the file data, output data or create a form, and save the XLS format document,

In these environments can be normal operation:
1. The Windows 7 professional 32 + 32 bit version of Office 2007
2. Windows 7 ultimate 64 SP1 + 32-bit Office 2007
3. Win10 professional version of 64 + 64 Office 2010
4. WinXP + Office 2003

CodePudding user response:

VBA have referenced content is lost, if you have deleted references again

CodePudding user response:

refer to the second floor zhui__ response:

VBA to have references to the content of the missing case, if you have deleted references again

There is no loss

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:

Right-click properties, compatibility, choose XP

CodePudding user response:

Compile time to declare "function" to "declare ptrsafe function"?
Just encounter this problem today, it is such a solution,

CodePudding user response:

So do not ask questions to you really rare, like the following people who don't know the building Lord what specific problems just answer the more rare,

CodePudding user response:

An error? The lack of any ocx

CodePudding user response:

The original poster hello, if the original poster programs written in the API reference, such as the declare the function, such as/sub in a 64 - bit environment, to add SafePtr operators, as well as those Long variable, all want to change to LongPtr, but these things cannot exist in a 32-bit DLL,

CodePudding user response:

references to the tenth floor sniperhgy response:

the original poster hello, if the original poster programs written in the API reference, such as the declare the function, such as/sub in a 64 - bit environment, to add SafePtr operators, as well as those Long variables that should be changed to LongPtr, but these things cannot exist in a 32-bit DLL,

You said "LongPtr" problem, it is a 64 - bit environment called 32-bit API only USES "source",
And the building Lord says is "VB program," for the compiled exe program, VB6 or VB.NET, is a "no LongPtr problems",
LongPtr exist only in the "source code"...

CodePudding user response:

The building Lord how no reply?