Jason,
You should be able to connect to PostgreSQL as an ODBC data source, which
will allow you to use the Access File->Get External Data->Import menu item
to select your PostgreSQL database, select the tables you want to import and
bring them into Access. This can be automated using VB or (I think) Access
macros.
Additionally, you could use File->Get External Data->Link Tables to set up
a link to your database, and use it to pass only certain records back and
forth to your PostgreSQL database, which can also be automated.
Without knowing exactly what you're doing, the best solution would probably
not be to synchronize the data, but to just link the PostgreSQL tables into
Access as tables and use them natively in Access, which is what we do where
I work. This allows you to use the Access reporting system, it's creepy
query builder, Access forms, etc. directly against your main database
without having to worry about synchronization.
If you are going to link the tables into Access you might want to let this
inform your table design decisions; for example the Text type in PostgreSQL
maps to Memo in Access, which isn't linkable or sortable under some
conditions, meaning that if you need it linkable or sortable it's best to
use varchar(255).
Just my 2c.
Thanks,
Peter Darley
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org]On Behalf Of Jason Watkins
Sent: Monday, January 28, 2002 9:29 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Moving my business to PostgreSQL
While none are ideal, it looks like I can meet my postgre failover needs by
a variety of methods. What about occasional (a few times daily) sync between
access and postgre? I could write my own scripts that spit tuples back and
forth over ssl, but there's gotta be something out there that can facilitate
this.
jason
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
