I have some subrecords with a text field that shows the following:

LE Name = Size:
2' 6" x 4' 6"   (pasted into this message from the actual sub-record)

I used the following command to seperate the width from the length.

vsize1 = split(size, "x")
vsize2 = size

this has been working great, but only on records that I added manually. It does not work on records that I imported from a .txt file. It seems that sesame cant find the 'x' to split, so it 'splits' the whole line and vsize2 gets a '0'.

I tried split(size, @chr(120))  as well as split(size, @chr(88)) and it doesnt help.

If I enter the LE and type an x over the existing x it works fine.??? Also, doing a search for '..x..' finds ALL the records.

What gives?

Steve

Your right,

I did a @replace(size, "x", @chr(88 )) and it seemed to replace them all to "X",  but still sesame can not detect the @chr(88 ) or @chr(120) or "x".

The data came from a q&a export file, saved as .csv then imported via programming into sesame.

Thanks,
Steve

OOPS.

Looks like the programming to replace 'x' with @chr(88 ) DID work after all.

I can now split(vsize, @chr(88 )) and its all ok.

Any idea how the 'x' stopped being an 'x' during the import?

Thanks,
Steve

Edit: It's odd how I can search and replace for this 'faux' X, but I can not use programming to Split the X. Does the Split command have some 'issues'? Is the split command case sensitive?

I plan to do a lot of importing 'splitting' and it appears the Split command is 'sensitive' to the actual character its looking for.

Shouldnt Lantica make Split more 'lenient'?

Can you direct me as to how I can learn exactly what ascii character I'm looking at when I see 'x' in a .CSV or .TXT file?

Thanks,
Steve

Quote:


No! When talking about a delimiter, you should be able to be very specific, to avoid splitting in unexpected places. For your purposes, Split can take multiple delimiters. You can get both cases by using:
Split(vString, "xX")

Quote:


Use @Asc().