Howard Maidman wrote:
I too am using AutoNo. as primary key and cannot even get this to
populate itself in a subtable of a one-to-many even though I have
successfully created an accepted ref integrety with cascading updates
etc!

Anybody got any ideas?

What do you mean by "populate itself"? Cascade update updates *existing*
children records when the key field of the parent is updated. Cascade
delete deletes *existing* children records when a parent record is deleted.
Nothing ever causes children record to automatically be created. Is that
what you are expecting?

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com