One form for a Single Entry, and a popup for Multiple Entries...

[MackMan]

Hello.

I have two simple tables tracking Transactions...(attached)

One is used for tracking single transactions, and the other is used for tracking multiple Transactions...

TblTopLines (used for single transactions)
TblPostMultiples (used for multiple transactions for a continuous form)

I have a question that relates to the relationship of both above tables in regards to the following :

95% of all transactions are based on a single line only, so would rather keep things tidy and use only the one form.
Of the other 5% of transactions, I'd like another from to popup based on TransactionType (in this case "Split / Multiple Transactions").

My Question is this...

I'd like the topLineID AND TransDate carried over to the popup form...on each line, but ...
I can get the form to open when "Split / Multiple Transactions" is selected and I can assign the TopLineID to only the top line of the continuous form, and all the entries below won't populate.
What have I done wrong?

 

[spikepl]

Your problems stem form the fact that you let user interface considerations spill over into your data structure.

You should have

tblTransactions - a table holding all info common to one or more transcations - date , account, PayeeID (yes ID - one payee surrely can have more than one transaction?)

tblTransactionDetails - amount (pos for credit, neg for debit) etc and the foreign key point at the right record in tblTransactions

 

[MackMan]

Thanks Spike. I had that design originally, but was wondering if it was possible to tidy up a bit so I played around a bit. I now have a form and subform to do just that, with no popups, and no data to carry over from one form to another. Just the two forms linked with the ID.