>All you advanced folks, skip this message. I've been having an interesting experience this week I wanted to share with other view newbies. All of the sudden it's easier to think of how to solve a problem using a view than using tables!
>
>I doubt I'm the only one who's had a time of it shifting from 10 years of thinking SET RELATION to SELECT/JOIN. But, if you're discouraged like I was, keep trying to use them when you can, because--voila!--all of the sudden it'll make loads of sense. My code is getting a lot more stable...make that understableable (George get's it < bg > ).
>
>Another note: sometimes it's cool to ease into this stuff!
>
>Regards, and happy programming

I've experienced this recently, and it does feel fine :). The latest thing was the place where I was simulating views, by making a r/w cursor with an additional field to keep the original recno(), and then if some manipulation on the cursor succeeded, GOTOed (or WentTo?) to original records and updated them. Now I made it all in just one view, which gets updated on success, or the changes are just discarded - the processing simply proceeds to the next possible value of view's parameter (parametrized, of course :), requery()ies and there we go again.

I've deleted lines and lines of old workaround code. Besides, porting old procedural code into a form was just cute.

Going views is only half fun - parametrized does it.