The prepare_for_sqlexec routine aids in getting ready for the sqlexec. Since I am building the sql into a variable, I have to stick quotes around a character value after performing rtrim. For numeric I have to convert to character. For null, I have to use "null". I will have to experiment with this.

Is there any easy way to compare two fields that can be null? Basically if both fields are null then return true, if only one is null and the other has a value then return false. If both are not null then compare the two values.

Jason

>It looks like you have quite a few variables for the timing the different operations. You should probably continue with that and figure out what is taking so long. Like Mike mentioned, maybe you will discover the SQLEXEC() within the SCAN() is the bottleneck, etc.
>
>Another thought I had when looking at all the code is what is going on in prepare_for_sqlexec(). Function calls like this can be expensive when you are making a bunch of them (just for the call alone, not to mention any code that is being executed). If you are doing a strtran() or something like that then it might be more efficient to just call strtran() directly instead of prepare_for_sqlexec().
>
>Something else you may be able to do is instead of calling sqlexec(), call mysqlexec() or something similar and send all the commands to a text file and then go execute the commands in Oracle (I don't use Oracle, but do you have something similar to Query Analyzer?). Obviously you will not be able to call mysqlexec() for command that drive the scans, etc.
>
>>The places I am doing sqlexec() are where I was updating various views. The views I had setup to updating based on pk only and had a batch count. When I was done all the changes I had a routine that ran through all the tables that were being updated which started a sql transaction, did the table updates and then did sqlcommits.
>>
>>I thought commands sent through sqlexec would be quite efficient since they are bring sent directly to oracle.
>>
>>Could the large number of sqlexec commands being run be the problem here?
>>