On Windows server platform, I open a VB development system (including SQL database), is now completely out hair, in the package to install to other computers in the LAN, the result is not used, the prompt database connection or something, SQL database still use Windows server SQL database, local area network (LAN) is the other computers in the XP system; I checked in the local area network (LAN) network Settings are not wrong, is in a network, and Windows server can PING each other make sense; VB database connection I am using the computer's IP address 192.168.0.2 in original machine test has any problems

VB own packaging procedures, can be packaged but in other computer and install, say what ADO version is wrong,

I chose several other packaging procedure, after the installation, run database junction don't, what ADO system version is wrong, or the network connection problem, trapped around me for a long time,

For some reason, I hope you help me to solve, thank you very much

CodePudding user response:

My dear friends, someone at?

CodePudding user response:

1, install the latest patches, SQL in SQL machine such as: SQL2000SP4
2, close the SQL machine firewall, including Windows built-in firewall
3, in the control panel of the ODBC client machines manually dispensing ODBC to SQL

CodePudding user response:

Windows SERVER and XP system will ADO version of the problems?
Haven't solve the problem

CodePudding user response:

Trouble you to help me have a look, urgent

CodePudding user response:

Should be: ADO component is not registered or version is wrong, but I'm from Windows server replication msado15. DLL to system32 xp computer systems at present, the register, it offers I can't find the file, but the file Ming is my copy to 32 now below, thank you very much
.

CodePudding user response:

Actually don't have to pack, bring very waste wood packaging program, you have only to the relevant documents copy directly to the past,
In running type regsvr32 msado15. Try a DLL

CodePudding user response:

Even the database, the general is the firewall system problem, assuming there is no question of your SQL SERVER on the SERVER, you can manually on the client to establish a connection to the database data source, see if I can connect. (control panel - & gt; Management tools - & gt; ODBC)
So it can detect whether a firewall blocking the SQL SERVER port.