>
>Just want to point that
>
>DO (cProcName)
>
>is faster and safer.
>
>Also, although I agree that this is a better approach than the DO CASE, I'm still concerned about the idea of several hundred similar procedures to maintain. Is there really no commonality that would let you cut this down to a few procedures accepting parameters?
>
Thank you for your input. I have since changed the approach and now working on storing the code in a memo of a table.
"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