VB & Database, VB6 (ADO) Front end to MS Access DB on Network Drive

VB6 (ADO) Front end to MS Access DB on Network Drive

Author

Message

James Hal
#1 / 3

VB6 (ADO) Front end to MS Access DB on Network Drive

I created a VB6 user input form that includes a custom ADO control. The
connection string accesses an Access 97 Database on another network
drive. I packaged it to the target network drive, then installed it to
my computer (where I developed the program) from that network drive. It
worked without any problems. However, I have a problem after I install
the program to another computer on the network (via access to the same
network drive from other computer). The program installs ok, but when I
try to run it, an error message states that the ActiveX component
couldn't create an object. The program runs, but it is not connected to
the database (nothing shows up in the bound text boxes). The ActiveX
control does show up on the form however. I tried mucking around with
the connection string, but I can't see why that would be the problem
since its the same database and the same path.

The provider and data source information for the connection string
should be the same because it's the same network drive, right?

The package should include ocx and DLLs that are necessary to run the
program, right?

Can anybody help me with this?

*** Sent via Developersdex http://www.*-*-*.com/ ***
Don't just participate in USENET...get rewarded for it!

Thu, 30 Dec 2004 08:44:32 GMT

Val Mazu
#2 / 3

VB6 (ADO) Front end to MS Access DB on Network Drive

Hi,

I think that you do not have that control included into your installation
package. You could check if your OCX was installed or not. Just try to find
that OCX file on your target PC. If it is not there then it is not
installed. Also possible that OCX file was installed, but was not registerd
on target PC. In that case try to register it manually using REGSVR32
utility

--
Val Mazur
Microsoft MVP

Quote:

> I created a VB6 user input form that includes a custom ADO control. The
> connection string accesses an Access 97 Database on another network
> drive. I packaged it to the target network drive, then installed it to
> my computer (where I developed the program) from that network drive. It
> worked without any problems. However, I have a problem after I install
> the program to another computer on the network (via access to the same
> network drive from other computer). The program installs ok, but when I
> try to run it, an error message states that the ActiveX component
> couldn't create an object. The program runs, but it is not connected to
> the database (nothing shows up in the bound text boxes). The ActiveX
> control does show up on the form however. I tried mucking around with
> the connection string, but I can't see why that would be the problem
> since its the same database and the same path.

> The provider and data source information for the connection string
> should be the same because it's the same network drive, right?

> The package should include ocx and DLLs that are necessary to run the
> program, right?

> Can anybody help me with this?

> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

Fri, 31 Dec 2004 20:01:53 GMT

James Hal
#3 / 3

VB6 (ADO) Front end to MS Access DB on Network Drive

The problem was related to the MDAC_TYP.exe. The control was dependent
on some data access objects that were not automatically packaged. I
made a dependency file that referenced the ADO control. This file
automatically included the MDAC_TYP.exe and installed its components
when the main program (form with ADO control) was installed.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

connection.txt
< 1K Download

Sat, 01 Jan 2005 06:10:26 GMT

Page 1 of 1

[ 3 post ]