That might work for Vendor, but it wouldn’t work well for a bill or a check. For example, I ran into a problem last night where after my web app inserts a bill record, it then tries to match the bill based on vendor and amount, but there were two bills with the same vendoer and amount, so later, when it tried to push in the billpaymentcheck, it failed because it was trying to apply it to the wrong bill, which had already been paid.
I have been linking things together using the TxnID or the ListID, but if those could potentially change at some point in the future, this is going to cause cascading errors of this sort in the future.
