In reviewing Alphasports I noticed that the extension price was a field in the table rather than a calculated field on a form. Up to now, I have thought that the calculated field for a form or a report was the prefered design. It saves a little in storage. Anybody have any strong views?
Also, I note a similar situation with the "ship to" check box. I don't readily see the design purpose and it doesn't seem to be used to speed up data entry.
On the "ship to" issue the design requirements have to cover various real requirements (at least for my business).
1. Ship to customers address (ie bill to and ship to the same)
2. Ship to address is different from bill to address.
3. Customer has more than one ship to address.
4. Customer wants it drop shipping to a third party.
5. Customer wants it drop shipping to a third party who is another of my customers.
From the above, my inclination is not to have shipto and billto fields in the customer table but to add each seperate address to the customer table and use a memo field to indicate which of the conditions 2-4 the entry is for, when it is not 1 or 5.
The invoice has a shipto field which is populated by the appropriate customer id field, with the default value set to that of condition 1 above.
Currently, the above requirements are only implemented in Alpha Four but as I struggle to move to A5 I was wondering if I need to make any changes in the design to the tables.
Steve
Also, I note a similar situation with the "ship to" check box. I don't readily see the design purpose and it doesn't seem to be used to speed up data entry.
On the "ship to" issue the design requirements have to cover various real requirements (at least for my business).
1. Ship to customers address (ie bill to and ship to the same)
2. Ship to address is different from bill to address.
3. Customer has more than one ship to address.
4. Customer wants it drop shipping to a third party.
5. Customer wants it drop shipping to a third party who is another of my customers.
From the above, my inclination is not to have shipto and billto fields in the customer table but to add each seperate address to the customer table and use a memo field to indicate which of the conditions 2-4 the entry is for, when it is not 1 or 5.
The invoice has a shipto field which is populated by the appropriate customer id field, with the default value set to that of condition 1 above.
Currently, the above requirements are only implemented in Alpha Four but as I struggle to move to A5 I was wondering if I need to make any changes in the design to the tables.
Steve
Comment