The big gotcha on linked tables in Access is that Access will "Background fetch" the entire table of any objects that
referencethat table on an open form. They try to throttle it so you won't notice, but you might.
Also, if you have Access queries that reference linked tables, Access will fetch the entire contents of all referenced
tablesbefore performing any joins/restrictions. That can really suck.
Another poster alluded to this when they suggested moving objects into Postgresql. Things like views.
It works fine, generally. Expect lots of harmless errors in your logs about how it can't find a certain system table,
andhow it keeps hanging up on Postgresql without closing the connection nicely.
>>> "Chris Ochs" <chris@paymentonline.com> 04/30/04 09:29AM >>>
We have a number of tables in a CRM that is written in MS access that I need
to be able to provide a web interface to. I can export the tables just fine
using pgadmin II, but I cant' think of a clean way to import them from
postgresql back to access. Synchronizing only needs to happen once a day
at the most.
I was also thinking of using the MS access forms with access tables that are
just odbc links to the postgresql database. Does anyone know off hand if
changing the MS access tables from a native table to a linked table would
require changes in the forms (not counting having to tweak/change data
types) ?
Chris
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.669 / Virus Database: 431 - Release Date: 4/28/2004
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org