Thread: RE: [HACKERS] MS Access upsizing

RE: [HACKERS] MS Access upsizing

From
"Ansley, Michael"
Date:
I believe Dave Page is thinking of putting that into pgAdmin, but you'll
need to check that with him.
Check on the pgAdmin page for features as well ->
http://www.pgadmin.freeserve.co.uk/

MikeA

>> -----Original Message-----
>> From: John Ridout [mailto:johnridout@ctasystems.co.uk]
>> Sent: Tuesday, September 28, 1999 7:31 PM
>> To: pgsql-hackers@postgresql.org
>> Subject: [HACKERS] MS Access upsizing
>>
>>
>> Hi,
>>
>> There is a very handy wizard for upsizing MS Access
>> to use MS SQL Server as a backend.
>>
>> Has anyone produced anything similar fro upsizing MS Access
>> to use PostgreSQL as a backend?
>>
>> Regards
>>
>> John Ridout.
>>
>>
>> ************
>>


RE: [HACKERS] MS Access upsizing

From
"John Ridout"
Date:
Thanks for the link.
Unfortunately the code is not open source.
I'll put a little something together this
weekend and stick it on my website.
See it we can't tempt a few MS Access users
to go for PostgreSQL instead of MS SQLServer.

Regards

John.

> -----Original Message-----
> From: owner-pgsql-hackers@postgreSQL.org
> [mailto:owner-pgsql-hackers@postgreSQL.org]On Behalf Of Ansley, Michael
> Sent: 29 September 1999 08:59
> To: 'John Ridout'; pgsql-hackers@postgreSQL.org
> Subject: RE: [HACKERS] MS Access upsizing
> 
> 
> I believe Dave Page is thinking of putting that into pgAdmin, but you'll
> need to check that with him.
> Check on the pgAdmin page for features as well ->
> http://www.pgadmin.freeserve.co.uk/
> 
> MikeA
> 
> >> -----Original Message-----
> >> From: John Ridout [mailto:johnridout@ctasystems.co.uk]
> >> Sent: Tuesday, September 28, 1999 7:31 PM
> >> To: pgsql-hackers@postgresql.org
> >> Subject: [HACKERS] MS Access upsizing
> >> 
> >> 
> >> Hi,
> >> 
> >> There is a very handy wizard for upsizing MS Access
> >> to use MS SQL Server as a backend.
> >> 
> >> Has anyone produced anything similar fro upsizing MS Access
> >> to use PostgreSQL as a backend?
> >> 
> >> Regards
> >> 
> >> John Ridout.
> >> 
> >> 
> >> ************
> >> 
> 
> ************
>