That's an interesting approach, I only use a cursor in one application's screen, the parent is an actual table and the child is a cursor, mine is significantly slower than using a table for a child, I use to have it that way, but I needed the information in separate records for processing and grouped for display. Are views a good choice for highly interactive programs?, what about refreshing and updating?. I've read here about people using views a lot, so there's gotta be something I'm missing, how do they handle updates?, is it done in real time?. Basically I had a lot of cuestions about the topic and using tables directly seemed simple and efficient, I use views for read only purposes but I'm always up for improvement, I actually started a thread about views vs tables last week I think.