When the invoice goes over $10000..it gives me #######...

[lrfowler]

I have an invoice in Access...............looks like it's not toalling the amount correctly.


Instead of $12600.00 it is ########
How do I fix this?

I am an extreme Access novice....

Where's Allen Bunch when I need him?

Larry

[JoeM]

It usually returns that when you haven't left enough space for all the numbers in your field. So if you widen it, you should be able to see the number.

[GeekInOhio]

That usually indicates that the actual field you have to display information isn't wide enough to display the data. Just make the field wider

[lrfowler]

sounds easy enuff.......which file format do I edit....and then what?

[John_G]

Hi -

You don't need to edit a file format. If the Invoice is an MS Access report, then what you need to do is widen the field where the ###'s are displayed. Widen it to the left, to keep the alignment correct.

John

[lrfowler]

I can't seem to edit the file............

[lrfowler]

never mind....that was real easy pa.....went into design view.....

[lrfowler]

umm......it's not fixed......I increased the size of the box in design view, but the form is still giving ######## as the total .......did I mention that the total is $12,000?
So I need to increase a field somewhere......probably the original file....mdb file ?

[John_G]

The problem is not the .mdb file or the data - it is in the report, and how it displays or calculates the total. Does the total display correctly when it is $500.00 for example?

What is your Format property setting for the control that contains the total? Is it using a larger font than other parts of the report, which would make it wider than you might expect?

John

[JoeM]

I assume the field is a calculated field. If it is, you may want to round the calcualtion to 2 decimal places using the ROUND function.
There is sometimes a floating arithmetic issue in the Microsoft products, and sometimes a calculation that should return something like $1200.00 might return $1200.00000000001 or $1199.9999999999999. That would push probably push it past the width you have set for the field. So if you apply the Round function to your calculation to round at 2 decimal places, that should correct that issue (if that is what is going on).