Importing Special Character from Excel Worksheet

darshanm
darshanm Member Posts: 280
edited 2006-08-14 in NAV/Navision Classic Client
Hi,

I want to import data from Excel worksheet into SQL server
through Navision data port. But Navision does not accept any special character from Excel Worksheet. After importing whole data
Navision shows like this "Polythene Bag 5?"" x 6?"""

How can import data with special characters??
Darshan Mungekar
Senior Consultan

Comments

  • kriki
    kriki Member, Moderator Posts: 9,127
    Use tabseperated-files.
    In the dataport put properties "FieldStartDelimiter","FieldEndDelimiter" to "<None>" and property "FieldSeparator"="<TAB>".
    The standard " as fieldseperator is not exactly the best choice.
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

  • darshanm
    darshanm Member Posts: 280
    Hi kriki,

    I have changed the dataport property, But still Navision is not
    accepting special characters. My data is as below

    Equal Tee 20mm ( ¾")
    End Cap 40mm ( 1½")
    Coupler 6 Kgs/Cm²

    How can I import the above special characters through dataport??
    Darshan Mungekar
    Senior Consultan
  • kriki
    kriki Member, Moderator Posts: 9,127
    Check this link:
    http://www.mibuso.com/forum/viewtopic.php?t=1774
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

  • jversusj
    jversusj Member Posts: 489
    darshanm,

    we were having similar issues and found the ansi2ascii converter to be an adequate solution thus far. Note, however, that we had to have our reseller do some map corrections so that we would get the right ASCII character. As we don't have the permissions to modify codeunits, this means we had to pay a few bucks for someone to make the change and get back to us. I would advise you do a lot of testing and make sure each special character is making it in unscathed.

    We were specifically having trouble with Ø being replaced with ¥.

    edit: we also had to have the Codeunit number changed to something within our license range (99999 would not work).
    kind of fell into this...

Categories