From jose@sferacarta.com Fri Feb 11 16:09:23 2000 Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA19507 for ; Fri, 11 Feb 2000 11:09:23 -0500 (EST) (envelope-from jose@sferacarta.com) Received: from proxy.sferacarta.com (sfcabop1.nettuno.it [193.207.10.213]) by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id RAA05180; Fri, 11 Feb 2000 17:08:50 +0100 (MET) Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5] by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian)) id 12JHBW-0001om-00; Fri, 11 Feb 2000 14:36:38 +0000 Message-ID: <38A41154.6CC13454@sferacarta.com> Date: Fri, 11 Feb 2000 14:40:36 +0100 From: Jose Soares Organization: Sfera Carta X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Chandra Wibawa , interfaces Subject: Re: Thank for your Clue - PostgreSQL ODBC References: <001001bf7301$5dec6c00$230039ca@prima.net.id> <38A16AE9.A95E79BF@sferacarta.com> <000d01bf748c$b02c4d00$230039ca@prima.net.id> Content-Type: multipart/alternative; boundary="------------F42F1F8D7ED9319C920C1DCB" --------------F42F1F8D7ED9319C920C1DCB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: > > > > > check off: > > > > > DataSource: > > check on. > > > > I hope this help you. > > Jose' > > -- Jose' Soares Bologna, Italy Jose@sferacarta.com --------------F42F1F8D7ED9319C920C1DCB Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

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
--------------F42F1F8D7ED9319C920C1DCB-- From chandraw@prima.net.id Tue Feb 22 05:31:11 2000 Received: from ns1.prima.net.id ([202.57.0.8]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA04849 for ; Tue, 22 Feb 2000 00:31:11 -0500 (EST) (envelope-from chandraw@prima.net.id) Received: from chandra ([202.57.0.35]) by ns1.prima.net.id (8.8.4/8.7.2) with SMTP id FAA01299 for ; Tue, 22 Feb 2000 05:32:33 +0700 (GMT) Message-ID: <001001bf7d17$798f0880$230039ca@prima.net.id> From: "Chandra Wibawa" To: Subject: Fw: Thank for your Clue - PostgreSQL ODBC Date: Tue, 22 Feb 2000 16:30:36 +0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01BF7D52.25B3E4C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 This is a multi-part message in MIME format. ------=_NextPart_000_000D_01BF7D52.25B3E4C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear SIr, I need your help about PostgreSQL ODBC. Please help me to solve the = problem Regards, chandra ----- Original Message -----=20 From: Jose Soares=20 To: Chandra Wibawa ; interfaces=20 Sent: Friday, February 11, 2000 20:40 Subject: Re: Thank for your Clue - PostgreSQL ODBC =20 Chandra Wibawa wrote:=20 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.=20 I remember this behavior the first times we started using = access->PostgreSQL but now I don't remember=20 why.=20 Send this mail to interfaces@postgresql.org, there is Byron Nikolaidis = the author of the ODBC driver, he=20 certanly knows this behavior.=20 Also take a look at the FAQ: = http://www.insightdist.com/psqlodbc/psqlodbc_faq.html=20 =20 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=20 ----- Original Message ----- From: jose To: Chandra Wibawa Sent: Wednesday, February 09, 2000 20:26 Subject: Re: Thank for your Clue - PostgreSQL ODBC =20 Chandra Wibawa ha scritto:=20 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 ?=20 M$ access is very slow but 45-60 minutes is too much=20 This seems like a net problem.=20 Anyway try to tune ODBC drive.=20 GO TO Options(Advanced)=20 Driver:=20 check on:=20 =20 =20 =20 check off:=20 =20 =20 DataSource:=20 check on.=20 =20 =20 I hope this help you.=20 Jose'=20 =20 --=20 Jose' Soares=20 Bologna, Italy Jose@sferacarta.com=20 =20 ------=_NextPart_000_000D_01BF7D52.25B3E4C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Dear SIr,

I need your help about PostgreSQL ODBC. = Please help=20 me to solve the problem

Regards,

chandra

----- Original Message -----=20

From: Jose = Soares=20

To: Chandra Wibawa ; interfaces

Sent: Friday, February 11, 2000 20:40

Subject: Re: Thank for your Clue - PostgreSQL = ODBC

=20

Chandra Wibawa wrote:=20

Dear Jose, Our server configuration = is :1.=20 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=20 version of PsqlODBC are you running? You need 6.40.0007.
I = remember this=20 behavior the first times we started using access->PostgreSQL but = now I=20 don't remember
why.
Send this mail to = interfaces@postgresql.org, there=20 is Byron Nikolaidis the author of the ODBC driver, he
certanly = knows this=20 behavior.
Also take a look at the FAQ: http://www= .insightdist.com/psqlodbc/psqlodbc_faq.html=20

Our network is = :1. Network Hub 10 Mb I have=20 followed your hints, it does improve the = performance. I=20 have done some testings, retrieving 3000 records from server to = client.I can=20 see the first hundred lines of the record, but when i scrolled down = the MS=20 Access windowit took a very long time to scroll down (5 minutes). When = i tried=20 to scroll to the last record, i had to waitfor ages, and finally when = i=20 pressed Ctrl-Alt-Del, i saw a message "not responding" on MS=20 Access. Could you tell me what = could be=20 done to overcome this problem ? Could this be the network, or the client = ? Thanks for your = help. Regards,Chandra=20
----- Original Message -----
From:=20 jose
To: Chandra=20 Wibawa

Sent: Wednesday, February 09, = 2000=20 20:26

Subject: Re: Thank for your = Clue -=20 PostgreSQL ODBC
=20
Chandra Wibawa ha scritto:=20
Thank's Jose, = I have succesfully connected my = database=20 (postgreSQL) to Access 97 on client machine. But I think there is = still=20 big problem because the link table takes takes too much time = (maybe around=20 45 - 60 minutes, even not responding).Would you mind give me = suggestion to=20 solve my problem ? For your=20 information, our configuration :1. Processor 133 MHz at client = side2.=20 Harddisk 1 GB at client side3. RAM 40 MB at client side4. Our LAN = speed is=20 10 Mbps
Is this your server or client ?=20
M$ access is very slow but 45-60 minutes is too much
This = seems like=20 a net problem.
Anyway try to tune ODBC drive.=20
GO TO Options(Advanced)
Driver:=20
check on:
<KSQO>
<Recognize unique indexes>=20
<Use declare/fetch>=20
check off:=20
<CommLog>
<Parse statments>=20
DataSource:=20
check on.
<Row versioning>
=20
I hope this help you.=20
Jose'

--
Jose' Soares
Bologna,=20 Italy &n= bsp; =20 Jose@sferacarta.com

------=_NextPart_000_000D_01BF7D52.25B3E4C0--