>That's interesting. I see your point for presenting a completely blank record for editing. Of course APPEND BLANK is the logical choice. What's interesting to me is the difference in user experience...I guess I haven't run into a situation where there isn't _something_ the user (or I) wants initialized. :-)

As long as you have the Primary ID added in the Default method Append Blank should be just as simple to implement as Insert.

The only exception I see is in grids using the built-in parent/child relations, where you MUST have the foreign key too. And if you're adding records to grids you deserve ALL the trouble you get < grin >. I've only done ONE app with grid editing, but it was a real hassle.