The best way of using FME Viewer would be to select Destination Data -> Redirect to Visualizer from the menubar and re-run the translation. That way you'll be seeing the data right at the very point of being written to Smallworld. If it looks OK there then I think Alfred is right that it's a GE issue.
Mark --- In [email protected], "alfred_sawatzky" <[EMAIL PROTECTED]> wrote: > > Hello Devendra, > > I don't know the actual solution to this problem, but I had two ideas > of what you could investigate. > - I wonder if you are running into an issue of text encoding with your > extra characters? > - What tools have you used to interrogate the source records > "first_owner_nm"? Did you use the FME Viewer tool? Using that tool > might give you an indication of whether FME is reading the extra > characters. If you do not see the extra characters in the FME Viewer, > then I suspect that your problem is with the Magik interface and you > could raise a case with the Smallworld help desk. > > Regards, > > Alfred Sawatzky > > http://sworldwatch.blogspot.com > > --- In [email protected], "dm_kulkarni" <dm_kulkarni@> wrote: > > > > Hello, > > > > I am running into an issue while trying to import shape file data > > into smallworld. > > > > The shape file field shows as char 96 when I check in FME as source > > dataset. I created a field in Smallworld object as ds_char16canon_vec > > (96) which shows up as char(97) in FME. > > > > But while translating, I am getting errors as "string too long, > > maximum 96 chars allowed" even though the source record from the > > shape has only 64 chars. So I put some debug_print statement in > > fme_tics_client.int!received_feature() and this is what I get > > > > sw:fme_alpha_field (:slotted ) > > sw:fme_alpha_field!name "first_owner_nm" > > sw:fme_alpha_field!type 1 > > sw:fme_alpha_field!value "VINCKIER RICHARD A&JACQUELYN M A-B > > REVOCABLE 1992 TRUST 11-25-92!<spa>u<backspace>" > > > > the source record shows value only upto "VINCKIER RICHARD > > A&JACQUELYN M A-B REVOCABLE 1992 TRUST 11-25-92". So there is some > > garbage data comining into the field and sometimes will break the > > translation. I also got some errors saying > > > > **** Warning: Failed to translate characters: %? > > text_converter_strange_input(real_string="?", string="%? ") > > > > However the source field value has no "?". > > > > Devendra > > > For insights into what's up at Safe Software and what's on the development horizon, visit Safe's blog at spatial-etl.blogspot.com. Safe Software has also made slides available that outline enhancements planned for FME 2007. The slides are from the "Road Ahead" presentation given on Day 2 of the FME Worldwide Users Conference. To view these slides, visit www.safe.com/2006uc. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/fme/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> 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/
