Public conn As ADODB. Connection
Public rs As the ADODB library you
When the FORM_LOAD
Set the conn=New ADODB. Connection
Set the rs=New ADODB. You
So have no access to 430 mistakes into and watch online a lot of people say mdac_type problem, after I use VB own packaging program packing not on any other computer installation (packaging manual joined mdac_type); Some say mdac_type version is too old, so I got off the covers mdac2.8 C plate mdac_type not repack again; Someone said using the setup factory packaging, into the mdac_type again at the end of the installation to run it, the result display system does not support directly, and I tried to run directly mdac_type2. 8 is a system does not support, I really don't have any choice, the program compiled for a long time, very not easy to realize the function, results are not used, the others really failed, hope to have the same situation of brothers and sisters to help, the younger brother grateful,
The last post, I the shadow in the engineering documents list, hope to help solve problems
Reference=* \ G {00020430-0000-0000 - C000-000000000046} # 2.0 # 0 # C: \ WINDOWS \ system32 \ stdole2 tlb# OLE Automation
Reference=* \ G {a7e9b0 50-70 ef - 11 d1 - B75A - 00 a0c90564fe} # 1.0 # 0 # C: \ WINDOWS \ system32 \ SHELL32 dll# Microsoft Shell Controls And Automation
Reference=* \ G {420 cf b2830 - E718-11-893 - d - 00 a0c9054228} # 1.0 # 0 # C: \ WINDOWS \ system32 \ scrrun dll# Microsoft Scripting Runtime
Reference=* {00000201-0000-0010-8000-00 aa006d2ea4} \ G # 2.1 # 0 # C: \ Program Files \ Common Files \ system \ ado \ msado21 tlb# Microsoft ActiveX Data Objects Library 2.1
Object={E95A2510 - F3D1 f840fe98091} - 416 - d - 823 - b - 4 # 3.0 # 0; The Command. Ocx
Object={BEC61919 - E6C4-11 d1 - BE7D - C63815000000} # 1.0 # 0; FLEXWIZ. OCX
Object={0 aa - 11 d0 ecd9b60-23 - B351-00 a0c9055d8e} # 6.0 # 0; MSHFLXGD. OCX
Object={831 fdd16 d2 - A9FC - 0000-0 c5c - 11 f8754da1} # 2.0 # 0; MSCOMCTL. OCX
Object={3 b7c8863 D78F - 101 - b - B9B5-04021 c009402} # 1.2 # 0; RICHTX32. OCX
Object={5 e9e78a0 cf - 531 - b - 11-91 f6 - C2863C385E30} # 1.0 # 0; MSFLXGRD. OCX
Object={F9043C88 - F6F2 b2f49fb} - 101 - a - A3C9-08002 # 1.2 # 0; Comdlg32. Ocx
The Object={BDC217C8 - ED16 CD - 956 - c - 0000-11 c04e4c0a} # 1.1 # 0; TABCTL32. OCX
CodePudding user response:
On the target machine, run the test code with respect to OK,CodePudding user response:
In addition to this method, no direct analysis of the reason? Now I'm not easy to find the target to testCodePudding user response:
Install a VirtualPc virtual machine, new clothes a xp system, the software deployment, see if you can run,If can not run, in the ocx DLL copy one by one, such as registration, until we can run up,
CodePudding user response:
Is your development on the use of ADO and target machine using ADO is not caused by the same version,First of all, in the development of machine to check the reference version of ADO,
Second, making VB installation package, usually in the installation package installation of the ADO,
Once again, can be installed on the target machine,
CodePudding user response:
From the above engineering properties file, use the ActiveX Data Object 2.1, change the reference to the ActiveX Data Object version 2.6 or higher try it.CodePudding user response:
This question, I have some engineering reference to add Microsoft ActiveX Data Object (i.e., its top version) 2.8CodePudding user response:
The original poster can be posted,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