Message-ID: <01C103DC.F1EE2890.mdavis@sevainc.com>
From: Michael Davis <mdavis@sevainc.com>
Reply-To: "mdavis@sevainc.com" <mdavis@sevainc.com>
To: "'Louisa Thue'" <lthue@navarik.com>, "pgsql-interfaces@postgresql.org"
	<pgsql-interfaces@postgresql.org>
Subject: RE: Question
Date: Tue, 3 Jul 2001 16:26:41 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

1. Yes
2. Using ODBC.
3. In some cases, yes.  In particular, if you use a lot of combo boxes on 
your Access forms and queries, they will be slow.  I took any tables that 
were accessed a lot and updated a little and copied them into Access.  I 
wrote a script that would refresh the local Access copy of these tables 
whenever the server copy of these tables were updated.  This was not an 
easy thing to do but it really helped the performance of many of my Access 
forms.

I hope this helps, Michael

-----Original Message-----
From:	Louisa Thue [SMTP:lthue@navarik.com]
Sent:	Tuesday, June 26, 2001 1:47 PM
To:	pgsql-interfaces@postgresql.org
Subject:	Question

I have a project where we take an existing Access 97 database, which has
already been divided into
front and back-end files, and converting the backend to a PostgreSQL
database.

My questions to you are:
1.  Is this feasible?
2.  If so, how would the Access front-end talk to the PostgreSQL
    back-end?  Using ODBC?
3.  Would this connection be painfully slow?

Thanks


---------------------------(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