reog error

I got an error message I've never seen before. In a SB V2.2 file, when I
attempted to reorganize, it failed. The error message states that the record
count changed & the reorg was aborted. Can anyone enlighten me? Thanks, Ben

Thanks Neil. I advised my client to have "SBLOCAL = NONE" in his
environmental variables under his user as well as system in XPP. Is that
correct? Ben
"Neil Robinson" <neilr@superbase.co.uk> wrote in message
news:e8119i$h1j$1@ipx22096.ipxserver.de...
> Ben Lieberman wrote:
> > I got an error message I've never seen before. In a SB V2.2 file, when
I
> > attempted to reorganize, it failed. The error message states that the
record
> > count changed & the reorg was aborted. Can anyone enlighten me?
Thanks,
Ben
> >
> >
> This can occur if there was a corrupted record in the file. That would
> cause the file to fail if reorganizing to the same name. Reorganize to a
> new name, then close and remove the old file (back it up somewhere),
> then reorganize back to the original name. These things can happen if
> you are using a multi-user version and don't have the server correctly
> configured.
>
> Ciao, Neil

Ben Lieberman wrote:
> I got an error message I've never seen before. In a SB V2.2 file, when I
> attempted to reorganize, it failed. The error message states that the
record
> count changed & the reorg was aborted. Can anyone enlighten me? Thanks,
Ben
> 
> 
This can occur if there was a corrupted record in the file. That would
cause the file to fail if reorganizing to the same name. Reorganize to a
new name, then close and remove the old file (back it up somewhere),
then reorganize back to the original name. These things can happen if
you are using a multi-user version and don't have the server correctly
configured.

Ben Lieberman wrote:
> Thanks Neil. I advised my client to have "SBLOCAL = NONE" in his
> environmental variables under his user as well as system in XPP. Is that
> correct? Ben

That is only part of it. If you have a multi-user system and the server
is running NT, 2000, XP, or 2003, then you also have to turn off
Opportunistic Locking. See the Networking Fact Sheet in the lower right
corner of the front page of the web site.

Neil,

What is the right info about Superbase.LocalFileLocking?

The fact sheet mentions setting it to false; however, the help says:

"To force Superbase to recognize all files as shareable, set
LocalFileLocking to -1 (True).
When Superbase starts, this property will be initialized according to the
following rules:
  The fLocalFileLocking property will be set to -1 (True) if one of the
following is true, in the order presented:
    If SBLOCAL is set to NONE in the DOS environment.
    An entry in the form of SBLOCAL=NONE is found in the Superbase section of
the SB30.INI file.
    If SHARE.EXE is loaded."

I've had it set to -1 for years on various systems, but I also usually provide a
tweak file for those with the data on a server.

The tweak file sets the parameters as recommended in the fact sheet:

REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Paramete
rs] "UseOpportunisticLocking"=REG_DWORD:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Paramete
rs] "UseLockReadUnlock"=REG_DWORD:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"EnableOplocks"=REG_DWORD:00000000
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmbParameters]
"OplocksDisabled"=REG_DWORD:00000001

If properly named, this file will dialog user for permission, then perform all
these settings automatically, when run. Needless to say, I don't give them the
proper name for this file without first having them back up their registry!

Peter






On Thu, 29 Jun 2006 14:30:54 -0400, Neil Robinson <neilr@superbase.co.uk>
wrote:

> Ben Lieberman wrote:
>> Thanks Neil. I advised my client to have "SBLOCAL = NONE" in
his
>> environmental variables under his user as well as system in XPP. Is
that
>> correct? Ben
>
> That is only part of it. If you have a multi-user system and the server
> is running NT, 2000, XP, or 2003, then you also have to turn off
> Opportunistic Locking. See the Networking Fact Sheet in the lower right
> corner of the front page of the web site.
>
> Ciao, Neil
>