|Subject:||Re: Help with writing tcursor
|Date:||Thu, 21 May 2020 16:33:57 +1000
|From:||Tom Krieg <REMOVEtomkCAPITALS@sdassociates.com.au>
One thing you need to realize. Do not, ever, allow an open tcursor to go
out of scope. Always explicitly open, edit, lockrecord and unlockrecord,
end edit and close tcursors. If you don't and tcursors go out of scope
say hello to memory leaks and GPFs.
On 21/05/2020 4:29 pm, Tom Krieg wrote:
> Don't use tc.locate, it can be tediously slow because it's a sequential
> read. Use a unique index or primary key and do a tc.qlocate for an
> instant retrieval. I gave up using queries back in '98 because my files
> were large and queries took forever.