Re: dBASE - DBF Tables - EXCLUSIVE MODE

Hi Arlindo.
I submitted this as QAID 6351

Thanks, kathy
QA
dBI

In article <1XL2icmQIHA.1912@news-server>, ac@apkomp.pt says...
> While SET EXCLUSIVE is OFF:
> The possibility of opening a table in READ ONLY mode when that table is 
> already open in exclusive mode
> 
> EXAMPLE:
>     USE example.dbf EXCLUSIVE (user 1)
>     USE example.dbf (user 2)
>         -> here opening the table in READ ONLY mode (much like what
happens 
> with MODIFY STRUCTURE when a table is already being used elsewhere) instead

> of error IN USE BY ANOTHER 
> 

In article <1XL2icmQIHA.1912@news-server>, ac@apkomp.pt says...
> While SET EXCLUSIVE is OFF:
> The possibility of opening a table in READ ONLY mode when that table is 
> already open in exclusive mode
> 
> EXAMPLE:
>     USE example.dbf EXCLUSIVE (user 1)
>     USE example.dbf (user 2)
>         -> here opening the table in READ ONLY mode (much like what
happens 
> with MODIFY STRUCTURE when a table is already being used elsewhere) instead

> of error IN USE BY ANOTHER 

I disagree with this request.  Using a table exclusive should only be 
used when absolutely necessary, for the minimum possible time, and 
therefore should not allow anybody else access to a table for anything.

-- 
Remove the ns_ from if replying by e-mail (but keep posts in the 

In article <bZCaxdnQIHA.1304@news-server>, ac@apkomp.pt says...
> >> for the minimum possible time, and therefore should not allow
anybody 
> >> else access to a table for anything.
> That should only happen when SET EXCLUSIVE is ON
> Using a table in EXCLUSIVE MODE is necessary for example to create indexes
> 
> ie.
> SET EXCLUSIVE OFF
> USE [table] EXCLUSIVE
> -> allows table to be opened elsewhere in READ ONLY
> 
> SET EXCLUSIVE ON
> USE [table] EXCLUSIVE
> -> does not allow the table to be opened

That's interesting; I never tried that experiment, and always thought 
that the results should be the same.  IMO, the second one is the correct 
result, while you obviously think the first one is how it should work.  
I could live with that version, but would prefer that it not work that 
way.


> 
> Thanks
> Arlindo Costa
> APKomp, LDA.
> 
> >><ns_dkerber@ns_warrenrogersassociates.com> escreveu na
mensagem 
> >>news:MPG.21d336286fbec695989dba@news.dbase.com...
> >> In article <1XL2icmQIHA.1912@news-server>, ac@apkomp.pt
says...
> >> While SET EXCLUSIVE is OFF:
> >> The possibility of opening a table in READ ONLY mode when that
table is
> >> already open in exclusive mode
> >>
> >> EXAMPLE:
> >>     USE example.dbf EXCLUSIVE (user 1)
> >>     USE example.dbf (user 2)
> >>         -> here opening the table in READ ONLY mode (much like
what 
> >> happens
> >> with MODIFY STRUCTURE when a table is already being used
elsewhere) 
> >> instead
> >> of error IN USE BY ANOTHER
> >
> > I disagree with this request.  Using a table exclusive should only be
> > used when absolutely necessary, for the minimum possible time, and
> > therefore should not allow anybody else access to a table for
anything.
> >
> > -- 
> > Remove the ns_ from if replying by e-mail (but keep posts in the
> > newsgroups if possible). 
> 
> 

-- 
Remove the ns_ from if replying by e-mail (but keep posts in the 

While SET EXCLUSIVE is OFF:
The possibility of opening a table in READ ONLY mode when that table is 
already open in exclusive mode

EXAMPLE:
    USE example.dbf EXCLUSIVE (user 1)
    USE example.dbf (user 2)
        -> here opening the table in READ ONLY mode (much like what happens 
with MODIFY STRUCTURE when a table is already being used elsewhere) instead 
of error IN USE BY ANOTHER 

>> for the minimum possible time, and therefore should not allow anybody 
>> else access to a table for anything.
That should only happen when SET EXCLUSIVE is ON
Using a table in EXCLUSIVE MODE is necessary for example to create indexes

ie.
SET EXCLUSIVE OFF
USE [table] EXCLUSIVE
-> allows table to be opened elsewhere in READ ONLY

SET EXCLUSIVE ON
USE [table] EXCLUSIVE
-> does not allow the table to be opened

Thanks
Arlindo Costa
APKomp, LDA.

>><ns_dkerber@ns_warrenrogersassociates.com> escreveu na mensagem 
>>news:MPG.21d336286fbec695989dba@news.dbase.com...
>> In article <1XL2icmQIHA.1912@news-server>, ac@apkomp.pt says...
>> While SET EXCLUSIVE is OFF:
>> The possibility of opening a table in READ ONLY mode when that table
is
>> already open in exclusive mode
>>
>> EXAMPLE:
>>     USE example.dbf EXCLUSIVE (user 1)
>>     USE example.dbf (user 2)
>>         -> here opening the table in READ ONLY mode (much like what

>> happens
>> with MODIFY STRUCTURE when a table is already being used elsewhere) 
>> instead
>> of error IN USE BY ANOTHER
>
> I disagree with this request.  Using a table exclusive should only be
> used when absolutely necessary, for the minimum possible time, and
> therefore should not allow anybody else access to a table for anything.
>
> -- 
> Remove the ns_ from if replying by e-mail (but keep posts in the
> newsgroups if possible).