nangko Posted June 17, 2008 Share Posted June 17, 2008 Hi, I often define global values that don't need to be changed as a calculation. I use this often for defining relationships. (for example a "0" key for defining an OR relation). I store the "0" as a calculation. So I can only change this value if I manage the database. And I don't need to create a form field first to give the global field a value. But what is better for DBPerformance? a global number field with the value "0" or a global calculation field with the calulation "0"? Link to comment Share on other sites More sharing options...
aaa Posted June 18, 2008 Share Posted June 18, 2008 Global number i think. Because global number have not place in all records and file have less size. Link to comment Share on other sites More sharing options...
Recommended Posts