>>>Nick,
>>>
>>>As I explained to you in another thread, you over-complicate your life. Since you're using cursors, you don't need to create unique names for them. Get rid of all names convenctions and macros and just use plain Cursor1, Cursor2, etc. names, or you can use something like CurToUpdate, curVals, etc.
>>
>>Nadya,
>>You don't know for sure if this level of complexity is needed or not. What if all processing takes place in one datasession? There may be a requirement to handle multiple result sets. Using the same alias (e.g. Cursor1, Cursor2) will close those work areas. IMO, you presume too much. You mentioned your opinion in the other thread; let it go.
>>
>>Just my $0.02.
>
>Ok. Still Nick can use evaluate function instead of macros, this probably would make this code more readable.

One reason I was using randomly named cursor was becasue this program will reside on a server, and serveral people may run the same method that creates these cursors. I have cleaned up the code as you recommended (I admit less complex), I just want to make sure that data retrieved by one user doesn't overwrite data retrieve by another user when using these cursors at same time. If these cursor are created dyanamically, can two people use same cursor name with different data for each users? If so, you've made my life lot easier to deal with. If not, the only thing I can think up is randomly named cursors.

Thanks
Nick Patel
"still learning the hardway"