D
dbeavon
Guest
Patrick, the second half of the program, after line 70 is the interesting part. It performs a simulation "server-side join" against the customers. It allows me to pull in any customer data that I may need (other than the CustNum which was found on the order). >> Why not run the query against TT_Customer? That is essentially what I'm doing. I'm generating a list of the required customers and querying them from the database in a single round-trip (by building a non-nested FOR EACH loop based on the CustNum). If I use the TT and do nested FOR EACH loops (or FOR EACH & FIND) then it would involve a hundred individual round-trips. Hope this is clear. FYI I tested the "-cache" to make the entire schema available to the client session. It does NOT seem to improve the behavior of "QUERY-PREPARE". The behavior of that "query-prepare" operation is quite disappointing. It repeatedly queries the same schema for the same table column (a hundred times, proportional to the number of customers in the WHERE clause).
Continue reading...
Continue reading...