Thanks,
Chad
Question
Special Charcaters in Access MDB file writer
+3- Contributor
I have a attribute name Unit # and the writer makes it and underscore. Is there a way to write out the special characters?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Hi,
seems like FME is a tad too agressive on the renaming, as "Unit #" is actually a valid field name in Access. Consider sending the case to Safe support if it's important to you.
On the other hand, I personally don't think it's a good idea to ever use spaces or special characters in field names. It has a tendency to always come back and bite you later, so I'd urge you to consider adopting something like "unit_no" instead.
Google "database field name conventions" for more ideas, there has been a lot written on the subject :-)
David
+3- Contributor
I agree on the special character as a bad field name, but the client sent me a template and I had to make mine match.
Thanks,
Chad
Hi Chad,
I understand your situation.
However, a field name containing some special characters is invalid in some softwares, not only FME. For example, a field name containing # cannot be defined in ESRI Geodatabase.
If the template could be modified through discussing with your client, I think changing the field name would be the best solution for the future.
Good luck! Takashi