>>>>>On a freash reboot of both server and workstation we can get a 0.4 second response time when doing a query. This response time continues until a second workstaion open the database, then both workstaions begin to get a 6.0 second response time, which continues until the next boot. Response time at the server console is always less then 0.5 seconds. Several workstations have been tried. Range is 486DX66 w/16M up to 200MHzPentium w/80M. Difference is less then 1 second.
>>>>
>>>>Nicole,
>>>> Is the query optimized?? I mean the following... Are there indexes that match the query conditions?? Is VFP building a cursor or is it just reopening the table in question again in another workarea??
>>>>
>>>>Please, more details are needed to help...
>>>>
>>>>Thanx!
>>>>
>>>>Tony Miller
>>>>Vancouver, Wa
>>>
>>>
>>>Thanks for the reply Tony. Although our system is slow in a number of areas I have attached the code for the area we have been timing. If we are making a fundamental mistake chances are we have repeated the mistake in a number of places. The following code is from the Valid event of a field where we enter a client code and press enter, then the program automatically fills in some information:
>>>
>>>IF field_change=0 THEN
>>> RETURN
>>>ENDIF
>>>
>>>** Display Lookup Values Associated with Selected Client Code
>>>
>>>vcode=ALLT(UPPER(THIS.value))
>>>IF EMPTY(vcode)THEN
>>> RETURN
>>>ENDIF
>>>
>>>THIS.value=ALLT(UPPER(THIS.value))
>>>
>>>RELEASE client_array
>>>PUBLIC client_array
>>>DIMENSION client_array(45)
>>>
>>>SELECT client_name,report_contact,po_number,report_address,report_address_2,;
>>>report_city,report_state,report_zip,report_phone,billing_contact,;
>>>billing_address,billing_address_2,billing_city,billing_state,billing_zip,;
>>>billing_phone,shipping_contact,shipping_address,ship_address_2,;
>>>shipping_city,shipping_state,shipping_zip,shipping_phone,account_number,;
>>>client_code,sales_person,reporting_name,billing_name,shipping_name,lab_rep,;
>>>discount_percent,surcharge_percent,client_notes,billing_code,;
>>>report_fax,report_no,invoice_no,track_number,project_number,project_category,hold,;
>>>inv_review FROM clients WHERE UPPER(clients.client_code)==vcode INTO ARRAY client_array
>>>
>>
>>It's here: using '==' is much slower than '='.
>
>Depending on the ANSI setting, no?

You know, the only way to have definite opinion about optimization is to test it. I just tested again and see that '=' is always better than "==", and Set ANSI OFF is always better than ON (in any combination).
I will appreciate any thoughts about it.