> > > I have no need for a design change - only to track this error.
> >
> > I'd like a sample application that demonstrates what it is you are
> > confronting so that I can see it.
> >
> > Thanks,
> > Jason Wharton
>
> If I had something which gave anything like a reliable problem I'd be hapy
> to send it but the error only occurs very infrequently. Always on
> application exit but maybe only once in 20 exits.
> It's obviously an attempt to relocate a record it can't so this
> smells like
> the closest I have been to the cuplrit for quite a while.
> If it goes away you'll never hear from me again :-)
>
> I was sadly under the illusion that Keylinks not only provided a way to
> retrieve records off the server but also to locate a record inside the
> buffer on the client side. It would appear now that no keylink is used for
> client location. And setting no keylink property should
> circumvent any such
> attempt anyway. I thought I read somewhere that an attempt to
> locate in the
> buffers was made first before retrieving a record from the
> server. So that's
> probably where I assumed wrongly.
> Alan
>

Well I just changed this SSP query to have no keylink, noautodefine and
raOpen.
Sadly, you get the Cursor unknown error straight away - it must be trying to
locate off the server - I'd like to stop it.
On the other hand, raKeepDataposition did work, the grid stayed in place on
transaction refresh so IBO DID successfully reopen the SSP and return to the
buffer record.
I'd just like it to swallow this cursor not found exception.
Alan