I have been using portals for a long time. But - never think of the connecting files as Parent and Child. I just want to make sure I have each one labeled in my head correctly.

For this example - I will use Invoices and LineItems. The invoices db has a portal to the lineitems for individual line entry.

The parent file would be the LineItems database and the child file would be the invoices databases. Correct? If I am thinking backwards - please let me know and help me to understand why it is the other way.

Thanks

Fifty-fifty odds and you blew it! (sigh!)

Remember, a parent can have many, many children, but a child can only have a limited number of parents.

Well -

Don't I feel pretty dumb at the moment. That makes total sense and should help me a whole bunch.

Thanks -

Dan

Reminds me of the time a friend called me ('cause I'm an "expert") because the word documents she created on her Mac couldn't be read on her client's PC.

I couldn't for the life of me figure out why. Once someone explained it to me...

The solution? She needed to append the ".doc" tag to the end of her filenames. I knew this, of course, and add extensions to all my files, but did I think of it when she asked me the question? Of course not!

Sometimes simple solutions are the most frustratingly hidden.