Re: Program design to minimize record locks

[Pete Helgren <Pete@xxxxxxxxxx>]

Cool.  WAY simpler than I expected. I stumbled over the two fields.  I 
read them as data structures but I can see how they are just fields.  
The "like" made me think they WERE DS's. 

I'll let you know how it turns out (busy "breaking" the code right now....)

Pete


Booth Martin wrote:
> Notice there is only one data structure.  The other two fields are just 
> chunks of space.  As to pushing your RPG skills, I'm suspecting that 
> after you do it and then look back at it you'll say something like "Huh? 
> That was simpler than I thought!"  :)
>
> To answer your questions:
> 1-Shouldn't be.
> 2-Yes
>
> I believe you have it all in your head excepting one small piece.  Your 
> thinking is correct excepting that since the two holding fields are 
> fields, not data structures, there is no conflict.  The FileNameDS does 
> in fact always have the most recently read data values, whether from the 
> original read(n), the screen exfmt, or the locking read.  You need to be 
> able to count on that fact to make the process work.
>
>
>