[[https://www.revelation.com/|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]]


==== Btree replacement (AREV Specific) ====
=== At 30 JAN 2003 08:06:32PM Michael J Moran wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
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.
</QUOTE>
----

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

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

</QUOTE>

----

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

<QUOTE>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...



</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=36B7D73ADEE1DA9F85256CBF00061789|View this thread on the  forum...]]