Updating tables in access Aunties chat

Ask yourself, "Would it be wrong if my field contained a value different from the calculation? If the difference would be meaningful, you do need the field.

If you are concerned about how a user could enter the calculated total with this arrangement, see Enter text in calculated controls.There are circumstances where storing a calculated result makes sense - typically where you need the flexibility to store a different value sometimes.Say you charge a construction fee that is normally an additional 10%, but to win some quotes you may want to waive the fee. In this case it makes perfect sense to have a record where the fee is

If you are concerned about how a user could enter the calculated total with this arrangement, see Enter text in calculated controls.There are circumstances where storing a calculated result makes sense - typically where you need the flexibility to store a different value sometimes.Say you charge a construction fee that is normally an additional 10%, but to win some quotes you may want to waive the fee. In this case it makes perfect sense to have a record where the fee is [[

If you are concerned about how a user could enter the calculated total with this arrangement, see Enter text in calculated controls.

There are circumstances where storing a calculated result makes sense - typically where you need the flexibility to store a different value sometimes.

Say you charge a construction fee that is normally an additional 10%, but to win some quotes you may want to waive the fee. In this case it makes perfect sense to have a record where the fee is $0 instead of 10%, so you must store this as a field in the table.

Do design your SQL Server tables for optimum performance with Access Make sure you follow my guidelines for designing SQL Server tables with Access: If you store your password with your linked tables you’re just asking for it if it falls into the wrong hands.

Instead use Ben Clothier’s method when linking tables, or recreate and delete them when your app starts and quits.

||

If you are concerned about how a user could enter the calculated total with this arrangement, see Enter text in calculated controls.There are circumstances where storing a calculated result makes sense - typically where you need the flexibility to store a different value sometimes.Say you charge a construction fee that is normally an additional 10%, but to win some quotes you may want to waive the fee. In this case it makes perfect sense to have a record where the fee is $0 instead of 10%, so you must store this as a field in the table.Do design your SQL Server tables for optimum performance with Access Make sure you follow my guidelines for designing SQL Server tables with Access: If you store your password with your linked tables you’re just asking for it if it falls into the wrong hands.Instead use Ben Clothier’s method when linking tables, or recreate and delete them when your app starts and quits.

]] instead of 10%, so you must store this as a field in the table.Do design your SQL Server tables for optimum performance with Access Make sure you follow my guidelines for designing SQL Server tables with Access: If you store your password with your linked tables you’re just asking for it if it falls into the wrong hands.Instead use Ben Clothier’s method when linking tables, or recreate and delete them when your app starts and quits.

instead of 10%, so you must store this as a field in the table.Do design your SQL Server tables for optimum performance with Access Make sure you follow my guidelines for designing SQL Server tables with Access: If you store your password with your linked tables you’re just asking for it if it falls into the wrong hands.Instead use Ben Clothier’s method when linking tables, or recreate and delete them when your app starts and quits.