>In a question I posed yesterday, I got the idea from Rich and Erik that I was doing something most developers don't do, so I wanted to get the straight scoop.
>
>Coming from a native VFP experience w/o views, I always assign my keys at record create as does the commercial framework I use for a lot of my projects.
>
>I got the impression from Rich and Erik that this is not usually done this way when dealing with views, but that keys are added in when a set of views (1:M:M...) are committed. What's the motivation for this? And Rich and Erik, if you're listening, does this make my earlier problem with orphaned grandkids go away?
>
>FWIW, I am trying to prepare my current project for easier upsizing, which is why I want to do it entirely with views.

I go ahead and assign a PK at creation time because I do not care if the user rolls-back the insert. My PK are also meaningless, the users never see these values in reports, forms, etc., and are always integer values. In one app, all invoice item records are committed immediately and can be deleted but not packed. The reason is the owner/managers want to be able to track which users added then deleted items from invoices. They can then compare inventory discrepancies to items deleted from invoices in case there is a theft problem.