You say you've tried the fields "formatted" as Currency, Percentage, and
Long Integers. Was the formatting or field size? Formatting affects the
display only, field size affects the actual numbers. For a Number data type
in a table, the possible Field Sizes are Byte, Integer, Long Integer,
Single, Double, Replication ID, and Decimal. Another option is to set the
Data Type of the field to Currency instead of Number. For your calculations,
I recommend that the Data Type be set to Currency then set the Format (in
the bottom pane) as desired. The Currency data type will give you more
accurate results in calculations because of the way the number is handled.
Next, why is the source for each a field in the table? Since you can
calculate one from the other, store one and calculate the other as needed.
By storing both, you are duplicating the information stored.

Signature
Wayne Morgan
MS Access MVP
> Hi Wayne,
>
[quoted text clipped - 14 lines]
> Both fields were formatted as currency & percentage, but I also tried them
> with no formatting at all. Couldn't tell a difference in the calculation.
r - 04 Aug 2005 17:07 GMT
Good point, Wayne - about not needing to store both values. Thanks. BTW,
fields are both long integers. I'll give it another try today, implementing
your suggestions. Thanks again!
> You say you've tried the fields "formatted" as Currency, Percentage, and
> Long Integers. Was the formatting or field size? Formatting affects the
[quoted text clipped - 32 lines]
> > Both fields were formatted as currency & percentage, but I also tried them
> > with no formatting at all. Couldn't tell a difference in the calculation.
Wayne Morgan - 04 Aug 2005 18:27 GMT
If the fields are long integers and you're trying to store values with
decimals, you won't get the right answers. You need a data type that will
accept decimals. Currency would be perfect for this.

Signature
Wayne Morgan
MS Access MVP
> Good point, Wayne - about not needing to store both values. Thanks.
> BTW,
> fields are both long integers. I'll give it another try today,
> implementing
> your suggestions. Thanks again!
r - 04 Aug 2005 19:15 GMT
Hm..
The fields I'm dealing with are in a subform that is set to Continuous.
When the field isn't bound to anything, ALL the percent fields get the
resulting answer of the calculation for the record being editted. Is there
a way around this??
Thanks.
-R
> If the fields are long integers and you're trying to store values with
> decimals, you won't get the right answers. You need a data type that will
[quoted text clipped - 9 lines]
> > implementing
> > your suggestions. Thanks again!
Wayne Morgan - 04 Aug 2005 21:30 GMT
Yes and no. You can do the calculation in the query feeding the subform.
This will create a calculated field in the query that you could then bind
the textbox to. However, the textbox won't be editable by the user.

Signature
Wayne Morgan
MS Access MVP
> Hm..
>
[quoted text clipped - 3 lines]
> there
> a way around this??