Homework assignment?!?!?! Jeez, Perry, I've been out of school too long to think about homework!!! < bg > (Altho, I did have a fun "homework assignment" about a month ago that I really enjoyed ... but that's a story that's better left untold ... < g >)

Of course, who am I to be able to resist a challenge? Guess I'll have to take you up on this (in all my copious spare time) ... that's the challenge, finding the spare time. < g >

-Bonnie

>Well then I guess we'll just have to give you a homework assignment to force you to get in the swing of things!!
>
>Since this is Views 101A, the first assignment will be something simple.
>
>1) Create a form displaying customer data with a grid whose record source is a view displaying orders belonging to that customer. (Hint: use a parameterized view)
>2) This one is for extra credit. Have the view access the products file to get the description for the item code in the orders file.
>
>There, that should get you started.
>
>Good Luck,
>
>PF
>>Thanks for the clarification, Jeff. I need to start playing with views ... I haven't used them yet in an app.
>>
>>>Bonnie,
>>>
>>>Like John said it depends on what you are trying to do. I use eView
>>>when creating parametitzed views because if you use the view builder and
>>>have an expression (field1 + field2)on the left side of the parameter
>>>you can not edit it. The view builder blows it away and makes you
>>>recreate it!
>>>
>>>But I also use GenDbcX for rebulilding the entire dbc and if I can
>>>figure it out to rebuild indexes on all tables.
>>>
>>>Moral of the story:
>>>eView for building views one at a time.
>>>GenDbcX for rebuilding DBC.
>>>
>>>Hope this helps.
>>>
>>>Jeff Whitaker
>>>
>>>>OK, so what's better (or at least how do they compare)... GenDbcX vs eView?
>>>>
>>>>-Bonnie