|
-
Oct 2nd, 2002, 01:58 PM
#1
Thread Starter
New Member
ActiveX DLL
Hi,
I have created an ActiveX DLL and addes some classes to it. when i keep it in debug mode and run my asp pages it works fine.
the compatibility is set to binary compatibility.
when i make the DLL and register ir using regsvr32 , it is giving me the following error
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
I have added all references to it. iam using the connection string as follows.
Provider='SQLOLEDB'; Data Source='ds';Initial Catalog='cc'; User Id='sa'; Password='sa';Integrated Security='SSPI';
any clues what could be wrong.
thanks,
soujanya
-
Oct 5th, 2002, 11:31 AM
#2
Hyperactive Member
How many machines are involved? That is, are you developing your site just on your development machine and not registering your component on another machine?
Are you getting that error as soon as you register your component using regsvr32?
Just making sure, you already know that when you "make" your DLL it registers it automatically on the local machine?
I tried you connection string changing the Data Source to the name of my SQL Server machine and the Initial Catalog to the "pubs" database, that worked fine. So it's safe to assume in your connection string you have a machine(i.e. the data source) named "ds" and a database(aka initial catalog) named "cc"?
If you are registering your DLL on another machine, does the other machine already have the VB Runtime dll's and all of the appropriate DLL's that your component needs? (like ADO)
-
Oct 6th, 2002, 03:07 AM
#3
PowerPoster
If you are porting your dll to another machine, it is more likely that your DSN "DS " is not present in the target system.
-
Nov 5th, 2002, 12:34 AM
#4
guys,
if you are registering a dll, the connection string would not matter. for the simple reason you could put any trash in the connection string and the dll would still compile.
yes it will certainly fail on use, but the compilation and registration would take place.
so i suspect that mdac is incorrectly installed on the target machine.
cheers!
abhijit
Everything that has a computer in will fail. Everything in your life, from a watch to a car to, you know, a radio, to an iPhone, it will fail if it has a computer in it. They should kill the people who made those things.- 'Woz'
save a blobFileStreamDataTable To Text Filemy blog
-
Nov 5th, 2002, 12:38 AM
#5
PowerPoster
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
The problem is that this error is more likely to be caused by a missing DSN, rather than a corrupt MDAC installation.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|