Heya Jeff -
42 seconds? thats nuts. You should have subsecond response time, mostly.
If across a WAN, ok- 12 seconds is about right.
I would suggest you got one or more of the following:
1. network contention
2. wrong sql protocols between the server and the workstations.
Workstations send one thing, server expects something else, doesn't get it
at first, then switches to the 'other' protocol .
3. SQL user logins to the SQL server not set right
4. wrong drivers at the workstation
5. improperly configured firewall throwing exceptions for the ms-sql port.
6. improperly configured router throwing exceptions for the ms-sql port.
You got access to the SQL Server at the DBA level? you'll need to look at
the connection types that it accepts, then compare those connection types
to what the workstations are using.
May be time to have a VFP / SQL Server expert do an audit at that site for
a day.
Warmest Regards [Bill]
--
William Sanders / efGroup {rmv the DOT BOB to reply}
VFP Webhosting? You BET! -> http://efgroup.net/vfpwebhosting
Failing dotNet Project? -> http://www.dotnetconversions.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
