D
dbeavon
Guest
@Brian - thanks for he pointer to SUBSTITUTE. That is helpful. I remember seeing that but haven't used it. @James - At least there is something that is internally compiled on the fly. The query string in the "QUERY-PREPARE" statement uses the ABL language, and that needs to be transformed into something that can execute on a CPU. That transformation is what I'm referring to. Here are the docs for QUERY-PREPARE: QUERY-PREPARE( ) method Compiles a predicate (query condition). It seems like it could be done once , and then swap out the value of the integer (iCustNum) on subsequent iterations. As things work today, it sounds like there is no other solution than to rebuild an entirely new query for each time I change iCustNum. Let me know if that is not the case. The QUERY-PREPARE is not a "free" operation, it is actually quite expensive from what I can tell, especially in relation to the amount of schema that may need to be retrieved over client/server networking.
Continue reading...
Continue reading...