Hi Sebastian,

I haven't written the routine yet, so I don't know whether it works or not. Your pointers are valid.

>what is this usefull for?

I'm thinking about designing a generic form that would ask for the values to plug into ?PARAMETERs. It will need to know what type data is needed. I was hoping that the ParameterList would be easier to maintain than setting up a table that listed all the parameters needed for each view.
After more thinking about it, I really need the table anyway. I will need captions, formats, etc. that the ParameterList can't provide.



>Hi, Bill!
>
>The VFP help file says:
>
>>>
>The format for the parameters is "ParameterName1, 'Type1'; ParameterName2, 'Type2'; ..."
><<
>
>But youre dealing only with "," as separators instead of using ";" as parameter separator - is this the problem?
>
>Some anothers hints:
>- Your lcList variable starts with a "," - may be this confuses VFP a little bit!
>- Is it ok to deal with "vartype(lcExpression)"? IMO you have to use "TYPE(lcExpression)".
>- What about all parts of lcexpression - do all parts exist in the moment of firing of "dbc_AfterModifyView"?
>- No possibility of having question marks in any string constants which could confusing the "occurs('?',lcSQL)" statement?
>- I think
> lcExpression =
> lcParameters =
>is to restrictive! What about expressions like "WHERE MyField = ALLTRIM( ?lcParameter )"?
>
>Summary: It will be a hard job to make this work in all possible circumstances!
>
>BTW: I never took care of this ParameterList - what is this usefull for?

Bill Morris