I always have the problem when adding to table in access via FME that it defaults to 20 chr strings for text. even if access is set to 255 chr strings.
If i have data going in that is more then 20 chr then it leaves it blank. but continues to populated others that are 20 or less. i cant recall if there are any errors but nothing that stoped my translation all together... i only notice when i look and access and see missing data. I use FME 2006 GOING BANANAS EDITION for a work around i just remember to increase the number in FME. :) -Regards -Shaun --- In [email protected], "mark2atsafe" <[EMAIL PROTECTED]> wrote: > > Hi Bill, > Kudos to Ray is what I say. > > You mean that FME had a defined size of 20 in the schema, and the > access database has 13, and because of this no data is written at all? > Even when it would fit in the 13 digit range? > > I did see a similar issue yesterday. With a Joiner the translation > stopped with ugly errors when the join attribute was longer than the > size of the Access join key. The ugliness of the error (apart from > stopping the translation with no good reason) was in telling me the > data types didn't match (incorrect). > > If you can confirm my interpretation of your problem then I'll ask the > developers to look into it. > > Regards, > > Mark > > --- In [email protected], Bill Voigt <bill.voigt@> wrote: > > > > Ray Kinser responded quickly with the problem. Thanks Ray. > > > > I had created attributes in Access of data type Decimal, but for > some reason, the width was set at 13, and the number of decimals at 2. > The default values for Decimal types are 20 and 10, respectively. I > still don't know why a value wasn't added, truncated to 2 decimal places. > > > > Once I reset the attribute to Double, the translation worked as > expected. > > I guess if one defines a destination dataset with garbage datatypes, > you also get what you asked for, even if it was not expected. It would > be nice in future versions to have some validation of data type > settings (perhaps a VERIFY button in the UserAttribute tab) to catch > these types of errors. > > > > -Bill > > > 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/
