>>>I switched from the first to the second, but it doesn't look like I gain a speed increase. I did multiple other changes, so it's hard to compare original code with the new code. But anyway, what do you think?
>>>
>>>Thanks in advance.
>>
>>I read the thread and you say it takes an hour for 4K+ records!!! Recreating a table from scratch, even writing byte by byte, with more than 4K+ would take much less than an hour. I don't think your problem would be solved by finding the nanosecond differences between these 2 approaches.
>>With even 255 fields and considering you would lıke to stay in old array limits you could cut down this to roughly 15-16 inserts for 4K+ records, if insert is really the bottleneck.
>>My .02 cents
>>Cetin
>
>Cetin,
>
>The program makes about 16 different inserts into 16 different tables in a scan loop. It also has some logic to check if it's the same patient, if the age it correct, is SSN is correct, does he/she has insurance, etc.
>
>I wish to send this program to someone for a quick review... I had the original code (procedural) which I converted to a class. I made couple of other speed improvements. However, it doesn't seem enough. I'm not sure what else can I optimize.

Converting it to a method of a class only slows it down.