Input Currency values being changed by ACCESS

[piperent]

Windows 2000 Pro
Access 2000 Version 9.0.2720

I have a record field declared as type 'Currency' that will not allow certain values to be input, i.e. Access will change the entered value to be some other amount.

Ex: I enter a value of 34.99, Access changes that to be 8.78. I enter a value of 26.99, Access changes it to be .78. I enter a value of 26.91, Access changes it to be .70. I could give example after example. The strange thing is, some values 'say 24.95, or 26.25, or 15.01 for example', are accepted without problems.

Anybody have any ideas what is going on? Anyone experienced this before? Any insight would be appreciated.


Thanks,
JP

 

[Bob44TheCat]

Hi JP,

Not sure what this means, but had you noticed that the difference between each of the three examples you gave is 26.21?
Presumably you're entering data into a form - is there some sort of calculation going on?

Hope this helps,

Bob.

 

[BoxHead]

How do you 'enter a value'? Form, query, procedure, typed into table, imported?

John

Use what you have,
Learn what you can,
Create what you need.

 

[piperent]

No, Bob4, I had not noticed the value similarity. I do know that no matter what transaction I change, if I change it to one of the stated values, i.e. 34.99, it will always change it to the 8.78 amount. In response to Boxhead, I do not perform any calculations of the field value on entry. It is just a simple value input.

I think I'll try deleting the entire File Layout, then rebuild it. I have to believe that something has gotten in and corrupted the structure. With no strict control in place, ACCESS has free license to format so many things to fit it's concepts. Somehow, they managed to conceive that I want a 26.21 adjustment on certain values. WHO KNOWS.

I'll report back after I try my approach.

Thanks for the time.
JP

 

[piperent]

Well, I give up. After deleting the 'tranaction' file layout and completely rebuilding it, nothing changes. Every time I enter '34.99', it converts it to '8.78'. Danged if I know.

I guess I'll just have to look for some other DB app to complete what I am doing. I don't have time to mess with this silly thing. ACCESS is neat, but if something goes hay-wire, your stuck. It's just a simple little Invoice Statement program, but I have a Tuesday completion deadline. No time to lose trying to figure out some goofy little Microsoft gliche.

What a bummer. ::-(

JP

 

[Lilliabeth]

After deleting the 'tranaction' file layout

What is a file layout? You are giving up too easily!

Give us more info. How do you enter data (a form or what)?

What tables do you have?

 

[BoxHead]

I fully agree with Lilliabeth.

Please, give us more info. If there's a bug, virus, setting or whatever that can randomly deduct $26.21 from a dollar amount entered, I need to know that I don't have it living in my system.

John

Use what you have,
Learn what you can,
Create what you need.

 

[piperent]

OK, OK, OK ............ :

Just to let you know, I haven't given up. But, I think I have figured out what's-a-goin on here. My system is built around an XFX motherboard. It's a couple of years old, and was geared more towards game systems. I THINK my problem has something to do with the chip-set involved with that motherboard. Here's what I did.

I completely deleted the 'entire' Invoice database from my machine. Halted, rebooted, then restarted ACCESS. From there, I totally re-built the entire database. Wasn't too hard since it only has two 'file layouts'. A file layout is contiguous with a 'structure' in 'C'. It is the format definitions for data held in a relational database file. Having completely rebuilt the database, I then populated the amount field with the '34.99' value. On my machine, it reflects that value back to me as '8.78'. But, when I converted the field to be 'integer', it converted it to the value '35'. This means the actual value was correct in the database, only the visual representation was being clobbered.

To verify all this, I moved the database to another system I have in the office, fired up ACCESS using the database from my machine, and guess what? The problem did not follow the database. That means that something is screwy either with my motherboard, or my W2K. At any rate, I think it has more to do with my system, hardware, and OS than it does with ACCESS.

I really appreciate you-all and the 'don't give up the ship' approach.

Thanks
JP

 

[jsteph]

Have you checked your Regional Settings, possibly a different currency language?
--jim