[V4MD] Importing text with high ASCII chars

[Bart Pietercil]

Hi Irv,

you really should try to download vStudio and import the tab delimited  
files through the import wizard.
Otherwise you could send me a testdb and an tabdelim file to import  
and I will try it out tonight (bart.pietercil(you know whAT)cognosis.be)
If you send it I also would like it in excel format

hth

Bart


On 01 Oct 2008, at 15:41, Irv Kalb wrote:

> Thanks Bart, Thorsten, and Ruslan.
>
> I should have explained a little more.  My client keeps all their
> data in Excel spreadsheets (one file per table).  They export the
> data from Excel into tab delimited text files.  I can clearly see
> these characters if I open the files in BBEdit.  I have written a
> utility program that reads all these files and creates  a new
> Valentina database file programmatically.
>
> I am not using Valentina Studio to do the importing.  And I am not
> exporting the data from an old V12 database,
>
> Thanks,
>
> Irv
>
> At 8:29 AM +0200 10/1/08, Bart Pietercil wrote:
>> Hi Irv,
>>
>> what codepage did you use to EXPORT the data from V12?
>>
>> The way we usually solve this kind of problem is opening the exported
>> file in excel (or Calc).
>> If the data look ok then save it again as windows ansi text.
>> Then import the data through VStudio. Set in the importwizard the
>> codepage to windows ansi
>>
>> hth
>>
>> Bart
>>
>>
>> On 01 Oct 2008, at 00:16, Irv Kalb wrote:
>>
>>> Hi,
>>>
>>> I've got all my tables built and all my code ported from V12 to
>>> Valentina!  Again, I appreciate all the help.  Only two more issues
>>> remain.  Here's one of them.
>>>
>>> In a number of fields, my original data includes high ascii values.
>>> Specifically, I have data that includes the following three
>>> characters:
>>>
>>>   165   bullet character
>>>   210   opening smart double quotes (slanted from left down to  
>>> right)
>>>   211   closing smart double quotes (slanted from right down to the
>>> left)
>>>
>>> When I import fields with these characters in them, they are
>>> converted to question marks.  When I look at them in Valentina
>>> Studio, they appear as a diamond with a question mark inside.  And
>>> when I retrieve the data from these fields, they come back as simple
>>> question marks.
>>>
>>> I'm assuming that this must be a problem with how I am importing the
>>> data.  These characters show up in both 'string' and 'varchar'
>>> fields.  I set up my tables with the appropriate creatStringField or
>>> createvarCharField statements.  Then I am importing a whole table at
>>> once with the following statements:
>>>
>>>   curs = gDB.SqlSelect( "SELECT * FROM " & sTableName, #kClientSide,
>>> #kNoLocks )
>>>   if CheckValError() then exit
>>>   curs.importText(sFileName, TAB, RETURN, "", TRUE)
>>>   if CheckValError() then exit
>>>
>>> The documentation says that Valentina uses "UTF-16" as a default,  
>>> but
>>> when I tried using "UTF-16" for the encoding, my Director program
>>> hangs and I have to force quit.  I found that using the empty string
>>> ("") allows it to work, but results in losing the high ascii
>>> characters.  How can I import text with these characters?
>>>
>>> I hope there is an easy fix for this one.
>>>
>>> Thanks,
>>>
>>> Irv
>>>
>>>
>>> --
>>>
>>> Multimedia R Us
>>> _______________________________________________
>>> Valentina mailing list
>>> Valentina at lists.macserve.net
>>> http://lists.macserve.net/mailman/listinfo/valentina
>>
>> _______________________________________________
>> Valentina mailing list
>> Valentina at lists.macserve.net
>> http://lists.macserve.net/mailman/listinfo/valentina
>
>
> -- 
>
> Multimedia R Us
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina