>>>I have used both cursors and parameterized views. Both have drawbacks and IMHO they shouldn't be necessary in VFP. Cursors can't be edited, and a parameterized view is redundant since one can define relationships between tables.
>>>
>
>Cursors are read-only if they are the product of the SQL statement. If you create them they can be read/write, but if you change any data in the cursor, you have to manually send these changes back to the table. This seems like a lot of work.
>
>My problem with parm views is that the number of views needed could grow out of control. Otherwise, I love them.
>
>Just my 2 cents (Canadian). .02 x .70 = .014$ :-)


These are the first negative comments I have heard about param views. And all this time I that this the way to go. I might suggest temp pv's if they seem to be getting out of hand. Or add a few more params to permanent pv's to make them more flexible so you would not have to create so many.

HTH