How to prevent Clearfile from resetting Sizelock (OpenInsight 32-Bit) [Revelation On-Line Wiki]

OpenInsight 32-Bit, Wayne Shepard, //www.sprezzatura.com]The Sprezzatura Group[/url], Barry Stevens, Don Miller - C3 Inc.

Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 14 MAR 2003 06:57:35PM Wayne Shepard wrote:

I'd like to use sizelock to freeze the size of a file, but every time I run clearfile prior to loading the new data, it resets the sizelock. I've tried it with sizelock set to 1 and to 2. Is there any way to prevent sizelock from being reset?

Wayne

At 15 MAR 2003 04:05AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Leave the sizelock set high and delete all the rows individually.

The Sprezzatura Group

World Leaders in all things RevSoft

At 16 MAR 2003 12:07AM Barry Stevens wrote:

Not sure if the CREATE_TABLE works on an exiting file, if so, you could use the "tableattributeslist" param to reset after the clear_table.

Barry

At 16 MAR 2003 08:34AM Don Miller - C3 Inc. wrote:

Not with the RTI-supplied tool but:

1. You can set the sizelock high and manually delete the records via a select/delete code segment. (Sprezz's suggestion)

2. You could encapsulate Clearfile in your own routine that would:
  a. Get the current sizelock value
  b. Call Clearfile
  c. Set it back when you're through
  You might have to offer a dialog to allow the user to leave the Sizelock alone or behave normally.  The danger in this is that you're messing with a system routine that might get overwritten in the future.
Don M.

At 17 MAR 2003 03:05PM Wayne Shepard wrote:

I planned to lock the file size in order to speed up the process of clearing and reloading the data. I figure if the size is locked, it won't have to keep restructuring the file as it loads. To turn around and select the records and delete them individually sort of negates everything gained, doesn't it? I suspect the number of records is a factor here. Do you (or anyone) know at what point the time lost deleting records individually exceeds the time gained by setting sizelock?