Ed,

I dropped each protocol and ran the tests with each one and except for IPX, nothing stops the performance from dropping.

I can see it happening, if I open on one pc a form with any tables set to optimistic row buffering, then on antoher pc go to another form with different tables in the same database set to optimistic row buffering, the performance immediately drops by 300%.

There has got to be some switch to set buffering up better on the NT 4.0 server.

John

>>David,
>>
>>This is a small LAN that is having the problem, NT server, 1 hub, 4 pc's with ethernet for all. TCP/IP and NetBUEI protocols. When the 2nd user gets in performance drops by 300% and stays that way until the everyone gets out and the 1st user can go back in, then user operates at normal speed.
>>
>>A similar network setup with Novell and IPX protocol shows no problems no matter how many workstations are in the app.
>>
>
>Try dropping NetBEUI and enabling NetBIOS over IPX/SPX, or if all stations are NT and/or Win98, eliminate everything except TCP/IP and enable NBT (NetBIOS over TCP/IP). It's crtical to drop out the NetBEUI since you probably can't be certain that the connection to the NT box is being done with TCP/IP when Win95 is involved.
>
>If you really suspect TCP/IP, enable NetBEUI on the server and don't use -any- TCP/IP on the LAN anywhere. This won't work if you're using the LAN to provide internet or IntraNet access that requires IP.
>
>>John Brooks
>>
>>>John,
>>>I would check your NT administrater and possible how your handling data across the LAN/WAN. I was running a 35 (10 people on local segment) person multi-user system across a T1 WAN with very little performance degradation. There was a large volume of transactions going across the T1 due to it being a real-time perpetual inventoring system.
>>>
>>>Thing that I did that helped:
>>>1) Create a normalized database.
>>>2)Placed executable and supporting file on an NT server on the other side of the T1.
>>>3) Loaded small (50 records or less),static, look-up information that is used through-out the application at start-up time.
>>>4) Used local view with table-buffering making sure to only read and write data when absolutely needed.
>>>5) utilized transaction processing.
>>>6) Used SYS(3051) to optimize SQL statements used in local views.
>>>7) Created supporting indexes on table to help optimize SQL statements.
>>>
>>>Hope this helps
>>>
>>>Dave.
>>>
>>>>Hi,
>>>>
>>>>I've posted this before but I'm really curious if anyone with mutli-user apps running on an NT 4.0 server and using Win95/98 workstations has seen large performance slow downs when multiple users are in the application.
>>>>
>>>>If you run TCP/IP protocol and more than one user is in the app performance drops by 300%. It looks like the problem is in the TCP/IP protocol.
>>>>
>>>>I really could use some help on this.
>>>>
>>>>Thanks,
>>>>
>>>>John Brooks