>Cetin,
>Sounds like a plan...but with the table I'm working with cursors aren't a good idea...IT'S HUGE!! I can't afford to lock up 10 Meg of RAM memory with a cursor. some of the PCs here are still using 16 Meg RAM (I have 64 M in mine and it slows up considerably). I'm still having a little bit of trouble understanding views. Where do they come into play, and how can a programmer use them effetively??
>
>Perry
Perry,
In fact cursors also reside on disk as temp files that are automatically erased as closed not in RAM. Views (until understanding fully) could be thought as virtual tables created from your base tables (like cursors definition held in DBC, know their source, editable, indexable etc).
Cetin