Stick to the view. What I do for complex views is run GENDBC against the database and then extract the part of the code specific to the view into a new PRG. Then change the SQL and run that new program vs. the current database and your view is changed. No mess, no fuss and screw that dad-gummed View Designer...

Although I'd like to plug Erik Moore's eView as another way to do this :-)

>Once again, my users want a major change. At present, a complex view offers the user a list of rooms that are available for occupancy. The users want to change the definition of available rooms considerably. As it is, it is not possible to modify the view 'sql staement to complex', so I am thinking a cursor might work better. Under normal circumstances, I would go ahead and try it, but as today is our No Sno Festival(AKA sillines day), it is the only chance I will have to get it done without users hassleing me. So, how much trouble will it be to change the datagrid that used the view over to a dynamic cursor? Or should I just stick to the view and change the way it gets populated?