 Home |
 Content |
| Purchase |
| Ready-to-use samples |
| Online resources |
| Forum |
| Links |
| Happy readers |
Anonymous
Still problems with $AssistAction (by Normunds Kalnberzins, 01/07/2005 03:10:16 AM) |  |
OK, I admit my previous answer to your post was grossly incorrect as that referred to $AssistRunInfo, not $AssistAction. Sorry for trying to mislead you.
I had a look as $AssistAction and it looks like a simple rich text field. Now while first record is simply CDPARAGRAPH, the second may be CDACTIONLOTUSSCRIPT -- for LS agents. It's a bit confusing that CDACTIONLOTUSSCRIPT has the same signature as CDTEXT, but they do not mix anyway. So that part of your analyses is correct.
Now what could you have done wrong. For all i can tell, today LS is being stored as LMBCS. One thing could be wrong -- you say you translate VB "native" to LMBCS. It should be "Unicode" to LMBCS as IMO VB "native" format is Unicode.
As a sanity test you could arange a "roundtrip" -- read the LS code, convert(ing it) to String, make sure it looks OK, then convert it back to LMBCS and compare with original buffer. But that's what you are probably doing. So the key IMHO is in correct Charset conversion.