Hi John and thanks for your reply.
I know it sounds queasy but this is one way required by the other division
where I work to have some sort of tracking dbase for their enforcement and
regulatory branch.
That is still no excuse for incorrect table design.
I have three tables: Company, License, and Machines.
One company may have many licenses - multiple licenses are required when new
machines are purchased. And one license may have many machines. So my form
boils down to a main form (company), subform (licenses), and subsubform
(machines) within subform.
Don't confuse FORMS - a data display and editing tool - with TABLES -
the data storage medium. I presume you have Tables in a one to many
relationship as well?
It is a privelege and in many instances where a
company buys other machines (such as poker machines) from another company.
So these machines need to be flagged down and transfer to another table
(company) who purchased these machines.
So there is a DIFFERENT TABLE for each Company? That's what doesn't
make sense to me. There should be just the three tables you named.
Transferring ownership *should* simply be a matter of changing the
value of a Foreign Key from the old company to the new company.
That's how this division wanted it
to be. Please let me know if you think there is another better way of
structuring this kind of requirement. I really appreciate it John. And let
me know if you need additional information and I'll be happy to provide you.
Yes, some more information would be helpful. What are the Primary Keys
of these three tables? Or are there more tables? How are the tables
related? What information needs to be transferred, and from where, to
where? Examples with real or dummy data would be very helpful.
John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps