Re: ovrdbf SHARE parameter

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

James

Yeah, seems I remember that - and isn't there a parameter on the OVRDBF 
command to keep your override independent of earlier ones? SECURE or 
something like that? Do you use that in this context?

Vern

James H. H. Lampert wrote:
> Vern Hamberg wrote:
>   
> > Of course, the type of open has to be 
> > the same throughout the call stack.
> >     
>
> But, as I discovered yesterday, you can override to SHARE(*NO) after 
> you've already got the file open once as shared, and open it non-shared 
> (even in the same call-stack entry!). At least if you're using the C 
> interface to record-level access. Which saves you, if you find out that 
> a file has been set to open SHARE(*YES) by default, from having to close 
> and reopen your first ODP if you need two separate ones. For details, 
> see my thread, "Strange problem with an _Rreadk()," on the C list.
>
> --
> JHHL
>