Hi - the trouble you are hitting is that different formats have different 'rules'. Particularly around column names formats are very pedantic. For example MapInfo Tab doesn't like column names to start with a number, Shape won't accept column names longer than 10 characters and sometimes specifies UPPERCASE column names only. As a result different formats react differently to different column name structures.

 

 

With databases things get even more hairy as you might have to also avoid reserved words too! 

 

 

http://forums.esri.com/thread.asp?c=93&f=985&t=286050

 

 

You'll need to try to trap the issues in your workspace... Transformers like the AttributeRenamer offer basic support and will allow you to create more acceptable attribute names for your intended target or perhaps names that are acceptable to multiple targets... but you may want to look at the SchemaMapper as a way to store your old names and their desired mappings outside of your workspace (useful for more complicated renaming).

 

 

Hope that helps...

 

 

P.s. Always avoid spaces, they cause lots of trouble!

---

Thanks for SchemaMapper tip, I think that is what i am looking for.

 

 

---

No problem. There's a little in here about the SchemaMapper about 35mins in 

 

 

http://www.youtube.com/watch?v=FObhAEwo6OM

 

 

But this might be more practical help:

 

 

http://evangelism.safe.com/fmeevangelist71/

 

 

Essentially:

 

The Feature Type Map = Move features from one layer to another

 

The Attribute Map = Is likely what you need as this is a more flexible AttributeRenamer

 

The Add Attribute Map = Is as you'd expect an AttributeCreator

---