Got some bad news dudes ...
I have a sml COM component that has a string property, when you send it a string, it loops over it and dumps the ascii contents, heres a sample:
code:
$ComString = CreateObject("ComString.String")
$ComString.String = "kixtart"+chr(1)+"org"
when i run this, the component dumps the contents as:
Dump string:
0=107
1=105
2=120
3=116
4=97
5=114
6=116
7=1
8=111
9=114
10=103
notice #7 that is the CHR(1) ... when I use CHR(0) instead, this is the dump:
Dump string:
0=107
1=105
2=120
3=116
4=97
5=114
6=116
7=111
8=114
9=103
notice the CHR(0) doesn't show up at all. Heres the sad bit, when I code this in VBS and pass it to the same COM component, the result is even worse than in KIX, it only seems to pass up to the CHR(0) and then stops.
code:
Set ComString = CreateObject( "ComString.String" )
ComString.String = "kixtart" & CHR(0) & "org"
the result is:
Dump string:
0=107
1=105
2=120
3=116
4=97
5=114
6=116
anyone know of another (proper) way to do this in vbs ?
-Shawn
[ 15. August 2003, 23:57: Message edited by: Shawn ]
