>>>>Along with the suggestions for programming optimization, I would suggest going with fater computers. I know this is sometimes easier said than done, but Pentium 120's are pretty slow computers by nowadaze standards...at least upgrade the RAM (I would first add RAM to the client and then to the server...the more the better). Also, Fast Ethernet (100Mbs) is no longer expensive...if you are not using it, that is one way to speed things up. I'd also suggest going to Windows NT if possible (maybe after upgrading the computers). I was never too impressed with Windows 95's networking.
>>>
>>>In my experience, you'll see no noticeable performance increase by going to 100BaseT from 10BaseT unless the delays are due to network congestion. In a previous situation I ran tests pulling data from SQL Server and the only time there was a performance increase (aside from the congested times as mentioned above) was when I was pulling a huge answerset (on the order of 30 Mb) from the server. Other than that, there was no difference either in pulling data from the server or using DBC/DBF on the networks (both NT and Netware 4.1)
>>>
>>>Christopher
>>
>>That would be because you didn't have a lot of network traffic. You were running client/server...meaning only the query information and the results pass along the network...if you are simply using a file server and a non-client/server application, entire tables have to be passed over the network to execute a query, so there will be a lot more network traffic. And then a 10X speed increase in the network will be noticable.
>
>Yes, I was running c/s, but that doesn't mean everyone else was. In fact, in this particular area, I was the only one running c/s.
>
>I've just never seen in my experience (which is quite broad) a significant performance increase by going to 100BaseT, certainly not as much as improving the file server configuration and the end-user machine configuration. 100BaseT is certainly worth putting in in any installation, but the real world performance gains are not that evident to the customer. In my 11 years of LAN experience, topology has always been the least effective remedy when it comes to price/performance.
>
>As I said in the first message, the exception to this is when the network is very congested. At that point, the topology change would be an advisable change. But this type of slowdown would be evident in every application that accessed files on the network and would not necessarily be a particular problem with the DBC/DBF access that he has mentioned.
>
>All I'm trying to say is that there are many ways to increase performance (with a much better price/performance ratio) before getting to topology, and those ways are usually more effective, again in my experience. Your mileage may vary.
>
>Christopher
Hi,
Thank your for your reply

1. Network : 10BaseT AND Ethernet
2. my app User : 5
3. my app is order entry system ( customer Data is about 13,000 rec and order data is about 15,000 rec )
4. when I using index(CDX) in my DBC , my app is same speed -> Slow :-(
5. my query -> "=SQLEXEC(nCon, "select cstno, cstnm, conm, copart, cotitle from customer where cstnm like 'choi%'", "tmp")

Pls help me

ASAP