Stephen,
The most common cause of this problem I can find is that MDAC did not
install properly (this is explained -in an SQL Server context - in MS
knowledgebase article Q191271). The fix suggested is to re-register
MSDASQL.dll eg.
C:\> C:\Windws\System\REGSVR32 "C:\Program Files\Common Files\System\ole
db\MSDASQL.DLL"
Alternatively try re-installing MDAC (http://www.microsoft.com/data/ado/)
Let me know if this works...
Regards,
Dave.
--
Network & Systems Manager, The Vale Housing Association.
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
Beer can be a permanent solution, but only if you have enough of it!
> -----Original Message-----
> From: Stephen Martin [mailto:stephen@sealteam.demon.co.uk]
> Sent: 04 October 1999 05:07
> To: Dave Page
> Subject: RE: [INTERFACES] pgAdmin v6.5.2 Released
>
>
> Hello,
>
> Heres the crucial excerpt from the VsErr.log
>
> Error Details
> *************
> Error No: -2147217842
> Error Description: Operation Canceled
> Error Source: Microsoft OLE DB Provider for ODBC Drivers
> DLL Error Code: 0
>
>
> I have both MDAC & DCOM98 installed
> I have seen the above error syndrome before with ADO based
> data objects.
> When ever I have in the past tried to interface a VB data
> object component
> with postgres ODBC driver I am always presented with an error claiming
> the required OLE DB provider for ODBC is either not present
> or corrupt.
> This has occurred on two separate pc's one running win95 the
> other Win98.
>
> My guess is something similar is happening here.
