Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Migration issue from 5.0 to 8.0

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
In the process of migration from 5.0 to 8.0.1 on windowsxp professional found the difference in the results with the following settings.
Help me to resolve this issue..it is an urgent ticket needs to be closed....

Output Data of 5.0 and 8.0
=====================================================

DATA:5.0 DATA:8.0
1,2300 1,2300
XXXX,00 XXXX,
77,334520 77,33452


======================================================
Source:

Item Subclass: Number
Interpret as: Binary
Presentation: Float
Length(bytes): 8


Target:

Item Subclass: Number
Interpret as :Character
Presentation: Decimal

Size:
Min :1
Max :14
Format: ####,##
Fraction syntax: Literal
Value: ,

Place:
Decimal min: 0
Whole# Min: 1
 
Forgot to add the rule iam using in the map.
TEXTTONUMBER( NUMBERTOTEXT( ROUND( objecttoconvert, 4 ) ) )
 
Did you open the tree in 8.0.1 and recompile?
Why do you need the rule, you should be able to do this with a drag & drop.


BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
 
I'm not clear on which bit of data your rule relates to - the only field with four decimal places is "1,2300" which hasn't changed from 5.0 to 8.0.

As per BocaBurger's answer, I would fix your rule and update the type tree - possibly you could change "Decimal min: 0" to a higher number? the current rule looks more like a workaround to a bug than good mapping.

What format does the target application need?

olly.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top