Sizelock (AREV Specific) [Revelation On-Line Wiki]

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 19 MAY 2000 11:52:26AM Rudhy wrote:

AREV Specific

What does Sizelock=0 or 1 or 2 mean ? Is that the only parameter for sizelock ?

Rudhy

At 19 MAY 2000 12:09PM Don Miller - C3 Inc. wrote:

Rudhy..

]]You asked
 What does Sizelock=0 or 1 or 2 mean ? 
The values are:
0=Allow file to expand / contract as necessary
1=Table may Expand, but may NOT contract.  This is what is set during resizing.
]1=Table may NOT expand OR contract. Note that this value is NEVER set by AREV but may be set manually or programatically.

HTH

Don Miller

C3 Inc.

At 19 MAY 2000 12:10PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

Sizelock is incremented when a select starts to warn the file not to resize. It can thus be any number. If however it is not 0 and a select is not taking place this could be a problem.

The Sprezzatura Group

World Leaders in all things RevSoft

At 19 MAY 2000 12:12PM Larry Wilson - TARDIS Systems, Inc. wrote:

Sizelock:

0 - file can expand or contract - I set all temp files to that

1 - file can only expand - the system downs' try to contract it when records are deleted (I set all of my data files to that)

2 - system does not try to expand or contract the file - I set all of my dictionaries, the SYSOBJ, WINDOWS, POPUPS, MENUS, and the VOC to that; it seems to speed up performance because the system isn't checking the file constantly to see if it needs to expand or contract. Of course, unless you write to, or select, the file, I don't think the system checks SIZELOCk anyway.

tardis_systems@yahoo.com

At 19 MAY 2000 01:15PM Larry Wilson - TARDIS Systems, Inc. wrote:

Andrew (I assume it's you),

Have you ever seen a problem?  I've been setting the sizelocks in my programs for years but have never noticed anything except a speed improvement.  However, if there is a documented problem, I would like to know about it.

tardis_systems@yahoo.com

At 19 MAY 2000 02:08PM Warren wrote:

Funny I thought sizelock=1 was that file would not expand or contract until a SELECT was run on the file (at which point the sizelock gets set to zero).

Sizelock is automatically set to 1 when a file is created. The rational for this is you may want to pre-size the modulo of the file and not have it resize during initial data population to speed the process up.

This left a 'trap' for the unwary as most people would not pre-size the file and it would be created with an intial modulo of 1 with sizelock on. The inital copy to this file could be quite slow due to all the overflow frames generated.

I always do a select on the file after creating it to clear the sizelock and not worry a fig about the time lost due to resizing. I do charge by the hour you know

At 19 MAY 2000 03:15PM Larry Wilson - TARDIS Systems, Inc. wrote:

That's a good idea about the SELECT after file creation, unless you presize the file. However, I've been using my own MAKETABLE so long that I forgot about that.

I charge by the furlong.

View this thread on the forum...