From: | "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp> |
---|---|
To: | "sow" <sowdog81(at)yahoo(dot)com> |
Cc: | <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Migration error: Provider not found |
Date: | 2003-07-31 03:33:39 |
Message-ID: | 01d801c35714$89042ae0$1f324d80@w2k |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Dear sow.
It is using Microsoft.Jet.OLEDB.4.0.
Jet 4.0 SP3 or higher (http://www.microsoft.com/data)
Regards,
Hiroshi-Saito
----- Original Message -----
From: "sow" <sowdog81(at)yahoo(dot)com>
To: <pgadmin-support(at)postgresql(dot)org>
Sent: Thursday, July 31, 2003 11:28 AM
Subject: [pgadmin-support] Migration error: Provider not found
> I'm trying to migrate a Ms Access 97 database to
> PostgreSQL 7.3.2 using pgAdmin II 's migration plugin.
> I running a windows NT 4 box with Access 97 installed,
> Jet 3.5 sp3 installed and MDAC 2.6 installed.
> Initially connecting to the remote Postgres server
> gave me the 'Provider cannot be found's but has since
> been resolved with the MDAC installation. After
> selecting the Access database which I intend to
> migrate , pressing next generates the error 'Provider
> cannot be found'. Please advise. Thank you
From | Date | Subject | |
---|---|---|---|
Next Message | frank_lupo | 2003-07-31 06:18:07 | Re: Problem with plpython editing |
Previous Message | sow | 2003-07-31 02:28:24 | Migration error: Provider not found |