PLS Help. Linked tables in MS Access

--0-910844804-1172486007=:87704
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear all, I am new to Postgre SQL, and have serious performance problem =
with Postgre SQL 8.1 as backend and MS Access 2000 / 2003 as front end ap=
plication. After searching archive in this maiing list, i found usefull i=
nformation like below. But i still have some big question :
=20
1. How can i know my ODBC driver version ?
2. How to run tcpdump ?
3. How to see Postgre SQL log, to see how fast it runs Access sql comm=
and ?
4. Some times when user input data, my application show "#delete" recor=
ds while no user delete record. How can this error appear ?
5. Could someone share his VBA code to connect from Access to PGSQL ? I=
think maybe something wrong with my VBA code that caused the "#delete" p=
roblem.
=20
The application run on both Access 2000 and Access 2003. So i use MS Ac=
cess 2000 file format MDB, running on A2000 and A2003, connect to Postgre=
SQL 8.2.3
=20
Thank you !!!
=20
Re: linked tables in MS Access
=20
---------------------------------
=20
From: "Philippe Lang" ) ch> =20
To: Jir=ED Nouza , postgresql ( dot ) org> =20
Subject: Re: linked tables in MS Access =20
Date: Tue, 23 Jan 2007 10:32:47 +0100=20
=20
---------------------------------
=20
pgsql-odbc-owner ( at ) postgresql ( dot ) org wrote: > Hello, > > =
I've read a post [1] about how MS Access is enjoyable and efficient > wh=
en tables are connected to MS SQL. > > But I have MS Access front end=
containing linked tables to Postgres > via ODBC. And I'm struggling wit=
h slow performance. When I want to > open a table which contains about 8=
000 records it takes more then 20 > sec. When I want to move cursor at t=
he last record it takes more than > 60 extra seconds. I'm not able to bi=
nd comboboxes directly to larger > (more than 60 records) linked table b=
ecause unrolling takes 20 sec. > All tables has defined primary key, o=
f course. > I was trying to change indexes without any result. > > I'=
ve already checked Postgres server log and MS Access queries are > execu=
ted quickly (<500 ms). > > Is this normal behavior? Does MS Access co=
operates with MS SQL such > better than with other DBMS via odbc? > =
> Does anybody have better experience?=20
> > I was trying to communicate from ASP.NET with Postgres via OLE DB =
> driver and it was without any performance problems. Hi, I'm usi=
ng MS Access, ODBC and Postgresql in several places, with big tables as w=
ell, and I don't have any performance problem. I have always been usin=
g the default driver parameters, and it always worked for me. But maybe y=
ou should play with that a little bit. And I think a few performance tuni=
ng tips have been discussed in this list in the past. One thing you ha=
ve to check, is wether you are using the MS Access 2000 format, under MS =
Access 2003. There is huge performance loss in this configuration. Conver=
t your database into the 2003 format, and problems will disappear. Sec=
ond thing: have you the opportunity to run tcpdump somewhere between the =
server and the client? You can activate the log of the server, too. This =
should give you useful "timing" informations. Cheers, Philippe =20

=20
---------------------------------
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.
--0-910844804-1172486007=:87704
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear all,

pgsql-odbc-owner ( at ) postgresql (

 dot ) org wrote:    > Hello,  >   > I've read a post [1] about =

how MS Access is enjoyable and efficient  > when tables are connected =

to MS SQL.   >   > But I have MS Access front end containing linked=

 tables to Postgres  > via ODBC. And I'm struggling with slow performa=

nce. When I want to  > open a table which contains about 8000 records =

it takes more then 20  > sec. When I want to move cursor at the last r=

ecord it takes more than  > 60 extra seconds. I'm not able to bind com=

boboxes directly to larger  > (more than 60 records) linked table beca=

use unrolling takes 20 sec.    > All tables has defined primary key, o=

f course.  > I was trying to change indexes without any result.  > =

  > I've already checked Postgres server log and MS Access queries are=

  > executed quickly (<500 ms).   >   > Is this normal behavi=

or? Does MS Access cooperates with MS SQL such  > better than with oth=

er DBMS via odbc?   >   > Does

 anybody have better experience?  >   > I was trying to communicate=

 from ASP.NET with Postgres via OLE DB  > driver and it was without an=

y performance problems.     Hi,    I'm using MS Access, ODBC and Postgres=

ql in several places, with big tables as well, and I don't have any perfo=

rmance problem.    I have always been using the default driver parameters=

, and it always worked for me. But maybe you should play with that a litt=

le bit. And I think a few performance tuning tips have been discussed in =

this list in the past.    One thing you have to check, is wether you are =

using the MS Access 2000 format, under MS Access 2003. There is huge perf=

ormance loss in this configuration. Convert your database into the 2003 f=

ormat, and problems will disappear.    Second thing: have you the opportu=

nity to run tcpdump somewhere between the server and the client? You can =

activate the log of the server, too. This should give you useful "timing"=

 informations.    Cheers,    Philippe =20