> Thanks to Frank Lupo and Hiroshi Saito for modifying frmSQLInput.frm. Now it >works good with writing plpython functions. >However the problem still remains with frmFunction.frm. For this form to work with >plpython we need to do the same work. I did try and works.
>
>
>
> Regards
> Lu
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" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 31, 2003 11:28 AM
Subject: [pgadmin-support] Migration error: Pro
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
Hi Luigi Lumento.
From: Luigi Lumento
> Thanks to Frank Lupo and Hiroshi Saito for modifying frmSQLInput.frm.
> Now it works good with writing plpython functions.
It was good.!
> However the problem still remains with frmFunction.frm. For this form to
> work with plpython we need to do the s
Donald Fraser wrote:
pgAdmin III July 16th Build.
OS: W2K SP4
There are loads of issues here and so I will start with just a few:
1) The only way to edit data is via view data. If I have a table that
has 200 records I don't want to load them all into a view.
The old pgAdmin II had the a
pgAdmin III July 16th Build.
OS: W2K SP4
There are loads of issues here and so I will start
with just a few:
1) The only way to edit data is via view data. If I
have a table that has 200 records I don't want to load them all into a
view.
The old pgAdmin II had the ability to edit da
