access2010
Registered User.
- Local time
- Today, 14:18
- Joined
- Dec 26, 2009
- Messages
- 1,021
Thank you for your suggestion.In a database it shouldn't matter what the value looks like in a table as long as it holds the correct value. Formatting is for forms and reports.
Attached is a database that stores the data correctly and has a form so that the user sees it in the manner you want.
Thank you for your suggestion.If your concern is that you want the user to be able to enter 4.5, then you could use a combobox linked to a lookup table with two Fields, one field containing the correct percentage value and another field containing the percentage value you want the user to see/display/select.
Alternatively you could have a pop-up form which allows the user to type in 4.5 but then converts the 4.5 to the correct percentage value and places that in the text box, and then have the text box format the value to appear as 4.5.
could you please send us a sample database?
Thank you for your note, our field is set up as;What errors do they make? I experimented with a number field set with percent Format and 1 decimal place. I type either 4.5 or .045 and both store 0.045 and display 4.5%. However, if I type 0.045 the value saved is 0 and 0% displays. Educate users to type 4.5.
Pat.single is a more appropriate size.
Use Format = Percent rather than standard
If you don't set the format to percent, Access will interpret 4.5 as 4.5 rather than .045
GasmanI must admit I am struggling to understand why any of you in the office cannot get this right?
You have been supplied details of what is required, you have been supplied a DB that shows it working and so what is needed, you have been supplied a video to also show what is needed. OK, you might not need percent on the table format, but I was expecting you to enter direct to the table as well?
So with a few small changes, you can get what you want working, but it seems to elude you.?
it does not seem to work in MsAccess 2003, which we are using.
Absolute NonsenseGasman
Thank you for your suggestion, but it does not seem to work in MsAccess 2003, which we are using.