Charlie

>>Using RV's requires permissions on tables. So, how would you stop someone who knows their password from running a delete statement against a table using an ad-hoc query program?<<

That's like saying, "To get into your house you need a key. How will you stop the burglar getting in if he has a key?" Well, you do your best to make sure he doesn't have the key. That a burglar with a key can get in is not an argument against locks, it is a management failure. Such failures are not exclusive to RVs.

>>I'm using SP's for all action queries. Each table in the database automatically gets its own set of update, insert, delete and select SP's. Moving this kind of code into SP's, IMO helps organize application development.<<

Perhaps. Question: if I have a table with 100 fields including 5 memo fields with big text strings and 2 general fields with (say) word documents in them, and all these need to be updateable as required... with RVs only the changed ones will be updated. With a SP, can you tell me how you will use SP to organise it more easily than using a Tableupdate() command and having it "just happen"?

Regards

JR