Problem Description:
------------------------
no warnings on DS 7.5 but warnings produced on DS 7.5.3 while using the same code
Warning: APT_CombinedOperatorController,1: Conversion error calling conversion routine date_from_string data may have been lost
Transformation used to convert DECIMAL(8,0) to a date
-----------------------------------------------------------------
If IsNull(lkread_L2OE.L2OE_INS_EFF_DATE)
Then SetNull()
Else (If DateToString(StringToDate(DecimalToString(lkread_L2OE.L2OE_INS_EFF_DATE,"suppress_zero") ,"%yyyy%mm%dd"),"%yyyy%mm%dd")="********"
Then SetNull()
Else StringToDate(DecimalToString(lkread_L2OE.L2OE_INS_EFF_DATE,"suppress_zero") ,"%yyyy%mm%dd"))
The results are as expected but I am getting warnings on the job-log, please let me know how I can get rid of these warnings
Warning converting decimal to date
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 145
- Joined: Fri Sep 21, 2007 9:35 am
- Location: Boston
-
- Premium Member
- Posts: 145
- Joined: Fri Sep 21, 2007 9:35 am
- Location: Boston
We are facing a similar issue when we upgraded from 7.5.1 to 7.5.3. recently.
There are no warnings on DS 7.5.1 but warnings produced on DS 7.5.3 while using the same code
Warning: APT_CombinedOperatorController,1: Conversion error calling conversion routine date_from_string data may have been lost
Does anybody know what causes this and the resolution apart from supressing the warning? I noticed that the warning went away when I handled the type conversion explicitly in 7.5.3. would that mean I would have to identify all instances where implicit conversion was taking place in the existing jobs and handle them appropriately?
Regards
Dhiraj
There are no warnings on DS 7.5.1 but warnings produced on DS 7.5.3 while using the same code
Warning: APT_CombinedOperatorController,1: Conversion error calling conversion routine date_from_string data may have been lost
Does anybody know what causes this and the resolution apart from supressing the warning? I noticed that the warning went away when I handled the type conversion explicitly in 7.5.3. would that mean I would have to identify all instances where implicit conversion was taking place in the existing jobs and handle them appropriately?
Regards
Dhiraj
Yes. They should have given you that same warning in the earlier version as well.dhiraj wrote:I noticed that the warning went away when I handled the type conversion explicitly in 7.5.3. would that mean I would have to identify all instances where implicit conversion was taking place in the existing jobs and handle them appropriately?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers