Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 30 JAN 2003 08:06:32PM Michael J Moran wrote:

Some time ago there was a btree replacement released on the REVSRC utility disks. The replacement overcame the 64kb limit.

A client has been using this successfully for a while, but now they are getting a few problems. One of the subroutines had a bug which I have resolved, but there is another subroutine which is getting an error during sort file merge when it calls V119. It does a couple of successful V119 merge calls, before it fails on the next V119 merge call.

Has anyone been using this btree replacement ?

Have you been able to overcome the V119 errors.


At 31 JAN 2003 07:39PM Curt Putnam wrote:

If you can't find anything obvious, put a garbagecolleect just before the calls to V119


At 14 FEB 2003 08:56PM Leon Shaffer wrote:

Anytime the user is running into the 64KB limit on AREV,

it is time to go to OI 4.x and do parallel (for a while)

runs of your application - OI does not have a limitation

on the data table, index table,

dictionary table (which would normally never exceed the

64K limit), etc.

OI will run 85 - 95% of your native code you have in AREV

and do it faster…etc….

OI 4.x is a fabulous product - and you still use your

same data that you have in AREV…

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/36b7d73adee1da9f85256cbf00061789.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1