UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Scaling of decimal value resulted in data truncation.    
 
   
repasky
post Aug 12 2008, 09:56 AM
Post#1



Posts: 184
Joined: 5-February 04
From: Pennsylvania


I get this “Scaling of decimal value resulted in data truncation." when moving a decimal value from a query to a new table. If the salary is 55000 it has no problem, but 55000.32 it get the error. Does the decimal not allow any decimal point unless there is a format defined? This is an easy fix, but the user would not be able to figure this out on their own and I am not going to be here after this week.
yT![fldCurrentSalary] = ![fldCurrentSalary]
thanks,
Al
Go to the top of the page
 
RuralGuy
post Aug 12 2008, 11:34 AM
Post#2


UtterAccess VIP
Posts: 2,833
Joined: 25-June 05
From: @ 8300' in the Colorado Rocky Mountains


The field in the table needs to be one that handles a decimal value. Single, Double, Currency.
Go to the top of the page
 
LPurvis
post Aug 12 2008, 03:15 PM
Post#3


UtterAccess Editor
Posts: 16,342
Joined: 27-June 06
From: England (North East / South Yorks)


Or indeed "Decimal".
So - what are the datatypes of *both* fields in question.
And if Decimal - what are the Scale and Precision of each?
Go to the top of the page
 
repasky
post Aug 15 2008, 10:01 AM
Post#4



Posts: 184
Joined: 5-February 04
From: Pennsylvania


That problem was with the data. A number was put in by mistake with a decimal point.
Go to the top of the page
 


Custom Search


RSSSearch   Top   Lo-Fi    30th March 2020 - 11:40 AM