"Ram�n Jim�nez" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Richard, > > If memory serves me right this is the opposite of what you were trying > to do a few days ago. If so, judging from your posted solution I suggest > you try this instead: >
Ramon thanks for the tip - I had tried something similar yesterday but had put the call in at the wrong place in the sequence of events. You also need to remove the line s serStr = serStr_"" as then serStr.GetStremId() fails with an <ILLEGAL OREF> error I have also found that you appear to be able to remove all the mysterious stuff referencing %qstrhandle without any obvious ill effects - does anyone have any idea what this does and why the docs suggest those lines should be present? Although it is still very early days in terms of what we are doing with this code, I did some performance measurements yesterday on my PC (1.6GHz P4), and we are seeing at least 100x faster compared to our previous architecture in both directions, which was way too slow to be deployable to customers. Richard
