Hi Bob,

It is a small network and all 15 computers go into a switch running 100MB NICS.

The code is extremely tight but there are a lot of look ups for lots of business rules.

I am very interested in this ODBC, to see if there are any significant gains in performance.

What are you opinions on doing the OLTP on the actual server or purchasing a "server" which has the data in locally and then clients access the data.

Regards
-Mark


>Mark,
>
>I would say some things you could do...
>
>1. Reduce the number of indexes you use on the OLTP portion of the application.
>
>2. What is the speed of your network? You could increse the network speed. Also, look at getting a high speed back bone with more switches connected to it. Or you could partition the network, put two or more NIC's in the server... this will cut the traffic on each LAN segment in half (if your traffic is fairly balanced.)
>
>3. You could consider going to a web front end. This will reduce the network traffic a tremendous amount. Of course, you would most likly have to re-write your UI.
>
>4. If you are doing alot of reporting, you may consider writting a COM object that runs on the server and processes report requests. Since the COM server will be running on the file server, and printing to the printer that will eliminate alot of network traffic.
>
>5. Analyze where most of the trffic is comming from. Perhaps you have a ZIP code table that is constanly used for lookups... you may want to put a copy of this table on the local PC. You can look at doing this with alot of your more static lookups.