Hi,
I did hear of one user who found that in certain situations DCOM95 was
required for MDAC2.0 to work properly. It's very difficult for me to test
these things because I have Visual Studio on my machines which of course
includes all these files.
DCOM95 is at: http://www.microsoft.com/com/dcom/dcom1_2/default.asp
You may need to reinstall in order: DCOM, MDAC, pgAdmin. If this doesn't
solve things, let me know.
BTW, pgAdmin will only work correctly with PostgreSQL 6.4.x
Regards,
Dave.
--
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!
> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Daniel
> Sent: 20 March 1999 00:23
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] problem with pgAdmin
>
>
> I need a management tool for win95 accessing postgresql 6.3.x
> running on a
> Linux box via ODBC. pgAccess currently doesn't work with ODBC so I
> downloaded pgAdmin. As required, I've also downloaded and
> installed the MS
> MDAC 2.0 (in custom installation, I didn't choose any of the database
> drivers their because I don't need them, except for the Jet engine
> component). Then I installed pgAdmin and it looked fine until
> when I tried
> to connect to the pgsql database. VSERR.LOG says:
>
> Error Details
> *************
> Error No: 3447
> Error Description: The Jet VBA file (VBAJET.dll for 16-bit
> versions, or
> VBAJET32.dll for 32-bit versions) failed to initialize when
> called. Try
> reinstalling the application that returned the error.
> Error Source: DAO.DbEngine
> DLL Error Code: 0
>
> I have reinstalled both MDAC and pgAdmin a few times and it's
> still the
> same. I've checked the file VBAJET32.dll and it is there.
> Postmaster -i is
> running, and PostODBC has already been installed and
> Powerbuilder 5.0 has no
> problem connecting to postgresql.
>
> What seems to be the problem? Please help.
>
>
> Daniel
>
>
>
>
>
>
>
