Glad you found a solution to your problem. yep, slick!

This is so typical of the UT...your ? prompted me to look at this area more closely, and it solved a problem I just started to work on...

thanks! J
>Jill,
>Right you are. Also you can use the DBSETPROP to set them first. Problem for me was that with several 100 views I just didnt want to waste 3 or 4 days doing all that...soooooo what I did was run the gendbcx program to create a .prg of my database...then I made another program that reads in that .prg (text file) and figures out what all the parameters are and automaticly stuffs them all in there with the DBSETPROP command..heh..pretty slick, huh?
>
>
>>Victor,
>>
>>It looks like you have to, in the View Designer, use the View Parameters option in the Query menu to tell VFP explicitly what kind of a parameter is expected.
>>
>>J
>>
>>>Ok...this doesnt work:
>>>
>>>DBGETPROP('myview', 'View', 'ParameterList' )
>>>
>>>Unless you've first done the matching DBSETPROP for it. I guess VFP doesn't do this for you automaticly I kinda wish it did.
>>>Anyway - so now my problem is that I've got several 100 views that need to have their parameterlist filled. Does anyone know of a little gizmo/utility that will do this for me or am I stuck making something?