Ok. I see what you mean.

I used a paramaterized view and I finally got the thing to work since you guys told me not to use append blank. :)

One thing I don't like is that I have to have a variable with the same name as used in the view for the parameter. For instance, I keep the client ID in thisform.cid, and when I want to requery the view, I need to do LOCAL cnum, cnum = thisform.cid, REQUERY(). That's a pain. I wish I could do REQUERY(thisform.cid) and have it fill in the parameters like that.

I also don't have a clue how to make a view outside the view designer, and some stuff I want to do is too complicated for the designer. I can see the syntax for programatically creating a view, but how do you get it in the database? Do you create it in the command window? Or do you need to run a program to create it each time you run the app?

Talk about getting off topic... :)

-Michelle


>Just that I've gone to using SET KEY TO in the child table instead of SET RELATION. The effect is that the child table iis ~filtered~ to match the parent record. So, it doesn't matter if you have the child or parent (or some other) alias selected.
>
>That said I'm actually starting to move my development to using parameterized views, but it's not always the quickest solution for me.
>
>I hadn't used SET KEY until someone mentioned it here. I *believe* it's faster than SET RELATION. I haven't done any benchmark testing on, though.
>
>>I got everything up to the last line. How does SET KEY TO come into this?