Fw: Thank for your Clue - PostgreSQL ODBC - Mailing list pgsql-interfaces

Chandra Wibawa wrote:

 Dear Jose, Our server configuration is :1. Pentium III 500, 256 MB, SCSI U2W2. SuSE 6.2, PostgreSQL 6.5.3 Our client configuration is :1. Pentium 133, RAM 40 MB, IDE2. Windows 98, Access 973. ODBC From Insight 
What version of PsqlODBC are you running? You need 6.40.0007.
I remember this behavior the first times we started using access->PostgreSQL but now I don't remember
why.
Send this mail to interfaces@postgresql.org, there is Byron Nikolaidis the author of the ODBC driver, he
certanly knows this behavior.
Also take a look at the FAQ:  http://www.insightdist.com/psqlodbc/psqlodbc_faq.html
 
 Our network is :1. Network Hub 10 Mb I have followed your hints, it does improve the performance. I have done some testings, retrieving 3000 records from server to client.I can see the first hundred lines of the record, but when i scrolled down the MS Access windowit took a very long time to scroll down (5 minutes). When i tried to scroll to the last record, i had to waitfor ages, and finally when i pressed Ctrl-Alt-Del, i saw  a message "not responding" on MS Access. Could you tell me what could be done to overcome this problem ? Could this be the network, or the client ? Thanks for your help. Regards,Chandra

----- Original Message -----

From: jose

To: Chandra Wibawa

Sent: Wednesday, February 09, 2000 20:26

Subject: Re: Thank for your Clue - PostgreSQL ODBC

 

Chandra Wibawa ha scritto:

Thank's Jose, I have succesfully connected my database (postgreSQL) to Access 97 on client machine. But I think there is still big problem because the link table takes takes too much time (maybe around 45 - 60 minutes, even not responding).Would you mind give me suggestion to solve my problem ? For your information, our configuration :1. Processor 133 MHz at client side2. Harddisk 1 GB at client side3. RAM 40 MB at client side4. Our LAN speed is 10 Mbps

Is this your server or client ?

M$ access is very slow but 45-60 minutes is too much
This seems like a net problem.
Anyway try to tune ODBC drive.

GO TO Options(Advanced)
Driver:

check on:
<KSQO>
<Recognize unique indexes>
<Use declare/fetch>

check off:

<CommLog>
<Parse statments>

DataSource:

check on.
<Row versioning>
 

I hope this help you.

Jose'
 

--
Jose' Soares
Bologna, Italy                     Jose@sferacarta.com