Hi,
FME itself shouldn't lose the leading 0 unless the field is ever treated as a
number.
You can check this out by using the Logger in workbench and examining the
values there. Perhaps in that way you can determine where in your
processing chain the 0 is being dropped and adjust it from there. The
concatenator itself certainly shouldn't drop it, nor should the joiner UNLESS
the field its joining to is numeric, then maybe that would happen.
If you're still stumped, please send a repro-package in to [EMAIL PROTECTED]
Dale
On 1/10/06, fme_user
<[EMAIL PROTECTED]>
wrote:
Hi all,
We are using FME 2006 Pro. Build 2173 reading in MicroStation V8
files. We are using text nodes inside polygons to build shapefiles
and
also link to an access database. The text node is the link to the
access database and consists of 2 lines of information. For example:
155
B707
In the workspace these two lines get concatonated to be 155_B707 to
create a link to the access database.
Sometimes the first line starts with a 0 and when FME reads this it
drops the preceeding 0. For example: 015 would be read as 15, as a
result it does not link to the access database which is looking for
015....
Is there a way to get FME to read the preceeding 0's?
Thanks for any suggestions,
chris
Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our
Professional Services team. Visit www.safe.com/services for details.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/fme/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details.
YAHOO! GROUPS LINKS
|
