>>>
>>>I think you do need to wrap it in TRY/CATCH. BTW, we do have the same function called RunSQL.
>>
>>Thank you for your input.
>
>In our application we're getting the same error as you do. I guess we would have to verify SET TABLEVALIDATE also. Let me know what else would you find in regards to this error.
I already put SET TABLEVALIDATE TO 7 at the top of my application (When Sergey talks I listen). And I added SET REPROCESS TO 10 SECONDS in every datasession (too bad you can't do it globally). I am also adding TRY/CATCH around the macro that executes SQL Select. Maybe there will be a day when I won't receive an error report {g}.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
