Sorry but I can't see the point of this at all. Maybe I'm missing something obvious?
Tables have unique names. Why do you need a unique long number field as well?
Perhaps you have developed a very clever way of managing your tables but, from the description you've given so far, to me it sounds like redundant data.
Possibly it would help if you uploaded something to help explain the idea.
The process described here is also useful for making User Edit Logs. All changes can be recorded in one Log Table.
We have taken the concept even further. Although, it has limited utility, and there are other ways to accomplish this:
We call this process Liquid Notes.
We have a Notes Table designed to house Memo fields.
we have Linking Table that has at least the following Fields:
tblUniversalLink
From:
ulUniversalLinkID
ulUniversalTableID
ulNotesID
it could be expanded to provide Universal to Universal "Many to many", literally
To:
ulUniversalToID
ulUniversaTableToID
The idea originally came from a need to to share Notes between Users and then make a connection to the Notes for the sake of keeping a trail of use. Like Customer Service may need to look at it and maybe when giving a refund or any number of other reasons. We use the one way one often, but the two way one which would allow child table flexibility may have never been used.
It seems that we have only ever needed to link one table's records with multiple Parent Tables, not multiple Child Tables.
I just looked at a Universal Link table; it was empty. So Multiple Parent, Single Child is the practical application.