Hi guys
I'm creating a relatively simple transaction DB for a small company so that they can log their outgoing transactions, and there are only 2 tables with a one to many relationship - one transaction can have many transaction items.
I'd created the tables and form(s), and then was informed that they'd like it to log the occasional incoming transactions too (90% of the database usage will be outgoing transactions). The fields for the incoming/outgoing transactions are basically exactly the same other than for incoming transactions, there will usually be only one 'item', instead of many.
They are not really DB savvy, but they suggested separate forms/tables for incoming and outgoing. This is obviously easy enough to do.
But i was implementing the querysearch system and creating the VBA and the forms and i thought - wouldn't it be better practice to simply have a 'transaction' table, and then an extra field which denotes if this transaction is an 'incoming' or 'outgoing' transaction - halving the number of tables and forms required. This could just be a drop down box in the form, with the default to 'outgoing'.
Of course, the user could then forget to change set this and then log the transaction incorrectly, but there are ways around this when creating the form.
Could anyone advice me on what the 'best practice' is to do here, with this kind of basic 'finance' database?
Many thanks!
Eddie
I'm creating a relatively simple transaction DB for a small company so that they can log their outgoing transactions, and there are only 2 tables with a one to many relationship - one transaction can have many transaction items.
I'd created the tables and form(s), and then was informed that they'd like it to log the occasional incoming transactions too (90% of the database usage will be outgoing transactions). The fields for the incoming/outgoing transactions are basically exactly the same other than for incoming transactions, there will usually be only one 'item', instead of many.
They are not really DB savvy, but they suggested separate forms/tables for incoming and outgoing. This is obviously easy enough to do.
But i was implementing the querysearch system and creating the VBA and the forms and i thought - wouldn't it be better practice to simply have a 'transaction' table, and then an extra field which denotes if this transaction is an 'incoming' or 'outgoing' transaction - halving the number of tables and forms required. This could just be a drop down box in the form, with the default to 'outgoing'.
Of course, the user could then forget to change set this and then log the transaction incorrectly, but there are ways around this when creating the form.
Could anyone advice me on what the 'best practice' is to do here, with this kind of basic 'finance' database?
Many thanks!
Eddie
Last edited:
