Aaron,
I spent a bit of time developing an Access app that may help called pgUpt
(http://dspace.dial.pipex.com/boylesa/pgupt/pgupt.shtml) that may help with
some of this. It aims to upsize all tables, provide an option to enforce RI
using triggers, creates indexes ... The tool was primarily designed for v 6
and some of the RI Triggers are now better implemented using DRI as Foreign
Key constraints.
I've not uploaded any updates to it for ages but I could send you an up to
date version if it if it would be of any use (the up to date version
includes code to autogenerate the Foreign Key constraints).
Regards
Steve Boyle
boylesa@dial.pipex.com
""Aaron Rouse"" <pgsql@happyhacker.com> wrote in message
news:030301c15d00$cedfa130$0301a8c0@win2kpro...
> I have the need to import an Access 97 database into PGSQL 7.1.3 It
has
> been a long time since I had to do this and back when I did, I just used
the
> PGAdmin tool which worked fine at the time with the exception of not
> converting AutoNumber data types to Serial, but to Int datatypes. I do
not
> see a way to import Access DBs with the new PGAdmin II tool and so far the
> only way I am finding to import the database is to import each table one
by
> one via a ODBC connection and the export feature in Access. This method
> still gives the same problem with the Autonumber datatype being converted
to
> Int and I am assuming it leaves out any indexes or default values as well.
> Is there another way to import this database that I might be missing?
>
> Thanks for any help.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
