Home > Software engineering >  Programs written in other computer can not run after compiling, for help
Programs written in other computer can not run after compiling, for help

Time:09-21

On the other computer when open the hint unexpected error, whether other computers on the lack of file
My program is mainly used to record,
The content of the reference such as the appended drawings


May not in any other computer with vb, excuse me, how to solve, I special leisure,

Programs written by the way, another set of window, close all Windows after the program is still running in the background, how to close the window when the program to close with

CodePudding user response:

Please reply,,,,,,,,,,,,,,,,

CodePudding user response:

1: make the installation package, rather than copy exe, vb own packaging tools,

2: make sure to close all open object, with End to End process

CodePudding user response:

Make the installation package still can't run, other computer prompts by unexpected error into Chinese "unknown error", running on their computer, there is still no problem

CodePudding user response:

Estimate that is a lot of your program code On the Error Resume Next,


VB6 code, in the case of without exception handling, basically will eventually be captured with a VB virtual machine to run the exception and indication error details,
Like you this kind of "refers to the type of object", if there is no corresponding "other" computer ActiveX DLL, no corresponding object type registered in the system,
When you need to create the object, but not successful creation, are generally will quote "a runtime exception" :
"ActiveX components can't create object" information (information is basically the "mean"),
Not so wrong after the "unexpected exception",


Solution of course is to understand your this program at run time,
What specific use the DLL (the key is you refer to the corresponding DLL library),
In "the other" machines, copy it to the system directory as an administrator, and register,

CodePudding user response:

May be ado2.8 conflict, need to use the method of TLB now I x64, x86 computer compiled twice, or just below the xp compile

CodePudding user response:

Development under Win64 a 32-bit program is the rhythm of the fault,

CodePudding user response:

Put your project in WinXP under the compilation and packaging,

CodePudding user response:

refer to 6th floor zhao4zhong1 response:
development under Win64 a 32-bit program is the rhythm of the fault,


Nonsense!!!!!!
According to this logic, you the VB6 can not be used in a 64 - bit system?

But the objective fact is that I in Windows 7 ultimate and Win10 pro under the two 64 - bit systems,
Installation, using VB6 simplified Chinese enterprise, as well as the compiled program, there is no problem,

CodePudding user response:

refer to the eighth floor Chen8013 response:
Quote: refer to the sixth floor zhao4zhong1 response:

Development under Win64 a 32-bit program is the rhythm of the fault,


Nonsense!!!!!!
According to this logic, you the VB6 can not be used in a 64 - bit system?

But the objective fact is that I in Windows 7 ultimate and Win10 pro under the two 64 - bit systems,
Installation, using VB6 simplified Chinese enterprise, as well as the compiled program, there is no problem,

can under XP install and use?

CodePudding user response:

refer to the eighth floor Chen8013 response:
Quote: refer to the sixth floor zhao4zhong1 response:

Development under Win64 a 32-bit program is the rhythm of the fault,


Nonsense!!!!!!
According to this logic, you the VB6 can not be used in a 64 - bit system?

But the objective fact is that I in Windows 7 ultimate and Win10 pro under the two 64 - bit systems,
Installation, using VB6 simplified Chinese enterprise, as well as the compiled program, there is no problem,


VB6 development program also can barely use;
The other day I met a shaft code farmer must Win10 under a 64 - bit system using VC + ADO development 32-bit Client, connection 32-bit SQL Server 2005, met play error dialog: "[DBNETLIB] [ConnectionOpen (SECDoClientHandshake ()).] SSL security errors,",
I advised him to WinXP under development, anyway don't listen,

CodePudding user response:

Ladies and gentlemen, my computer is Windows 7 32-bit system, and not as a whole sentence On the Error Resume Next, and other computer Windows xp and Windows 7 operation Error, is 32 bit, very simple database management programs, here can't upload attachments can't show it to you

CodePudding user response:

CodePudding user response:

Software is used to record a database, connect to public folder below a Shared database, want in each computer network can record and modification, after the completion of the record is copied to the local computer is used to query

CodePudding user response:

Audient00
reference 11 floor response:
, ladies and gentlemen, my computer is Windows 7 32-bit system, and not as a whole sentence On the Error Resume Next, and other computer Windows xp and Windows 7 operation Error, is 32 bit, very simple database management programs, here you can't upload attachments to see if
is backwards compatible operating system, so the software based On the old version can be used under the new version of the system, and may not necessarily, originally I double system is installed, one of the special Win98 presented to the user to compile the VB project, now have no Win98, but still kept under Win98 system file version, generated after the installation package, with the old system covering the same file, and then use the Support under the path of bat batch file to repackage,

You use Windows 7 build packaging, should be able to support the child version above is equal to your system version of the operating system, the other is to say, depending on the system files,

CodePudding user response:

nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related