hello all
I'm thinking about the best place to set certain properties in my database.
Lets say my table has a numerical field. If I set a property like 'Decimal
Places = 3' in the table, can I have confidence that this property will be
passed to any queries and ultimately to forms / reports? What if the
query/form/report tries to imposes a different value for the same property?
Is it best to set any given property for a field at the place where all
'downstream' uses of that field's value will be unchanged? just wonderin'
thank you
Damian S - 26 Feb 2007 22:57 GMT
Hi Victoria,
The benefit (and also challenge) of using Access is that as you have
discovered, you can set these properties in multiple locations. Personally I
set them all in the forms/queries as required rather than back at the table.
Other posters might disagree with me.
I guess you work out where you like to set them, and be consistent.
Damian.
> hello all
>
[quoted text clipped - 7 lines]
>
> thank you
onedaywhen - 27 Feb 2007 09:19 GMT
On Feb 26, 9:58 pm, Victoria <Victo...@discussions.microsoft.com>
wrote:
> I'm thinking about the best place to set certain properties in my database.
> Lets say my table has a numerical field. If I set a property like 'Decimal
> Places = 3' in the table, can I have confidence that this property will be
> passed to any queries and ultimately to forms / reports?
If you require three decimal places you should use the DECIMAL data
type with the decimal scale property set to three. Actually, you may
want scale = 4 to store an extra decimal place with which you can do
custom rounding (the DECIMAL type truncates values by nature).
Jamie.
--