 | |
Field display as ###### in A2010
comp.databases.ms-access comp.databases.ms-access
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Field display as ###### in A2010 -
09-21-2010
, 01:50 PM
#2
| |||
| |||
|
#3
| |||
| |||
|
|
?"paii, Ron" wrote in message news:i7auph$p94$1 (AT) news (DOT) eternal-september.org... In A97 if the data for a numeric or date field was wider the space provided on the form or report, it displayed the data that fit. In A2010 it displays ######. Does anyone know a setting to revert to the A97 output? --- That's interesting, access 97 is now 6 versions ago (inclusive) ? I'm not sure when they changed this behavior, but when you're dealing with things like amounts owing to a customer, bill payments, or amounts for patient dosages etc, not knowing the number your reading is being truncated can often have very serious ramifications in both practice and in a legal sense. You'll notice that even when a column is sized narrow, when the number can display you don't see ###, but ONLY for Those numbers that don't fit in the given size . You can certainly build a query, and convert that column to as string, and it does not exhibit that behavior for strings. So in the query builder you can type something like the following in : VID:str([ID]) That number column will not be editable if you do the above. Can't say this issue come up much here often and most as a general rule suggest one avoid editing data in a direct table view anyway. However, I can confirm this change, and I don't know when this change occurred. |
File ->Current Database -> Application Options -> Check for truncated number
fields. No idea what it does, but it looks possible
Phil
#4
| |||
| |||
|
#5
| |||
| |||
|
|
On 21/09/2010 22:36:54, "Albert D. Kallal" wrote: ?"paii, Ron" wrote in message news:i7auph$p94$1 (AT) news (DOT) eternal-september.org... In A97 if the data for a numeric or date field was wider the space provided on the form or report, it displayed the data that fit. In A2010 it displays ######. Does anyone know a setting to revert to the A97 output? --- That's interesting, access 97 is now 6 versions ago (inclusive) ? I'm not sure when they changed this behavior, but when you're dealing with things like amounts owing to a customer, bill payments, or amounts for patient dosages etc, not knowing the number your reading is being truncated can often have very serious ramifications in both practice and in a legal sense. You'll notice that even when a column is sized narrow, when the number can display you don't see ###, but ONLY for Those numbers that don't fit in the given size . You can certainly build a query, and convert that column to as string, and it does not exhibit that behavior for strings. So in the query builder you can type something like the following in : VID:str([ID]) That number column will not be editable if you do the above. Can't say this issue come up much here often and most as a general rule suggest one avoid editing data in a direct table view anyway. However, I can confirm this change, and I don't know when this change occurred. Have a look at File ->Current Database -> Application Options -> Check for truncated number fields. No idea what it does, but it looks possible Phil |
#6
| |||
| |||
|
|
Have a look at File ->Current Database -> Application Options -> Check for truncated number fields. No idea what it does, but it looks possible |
last week about Access I learned.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.