<div dir="ltr"><div>Okay - so here is what I did -- I double checked that all lookups to the main data file are in fact protected...but I noticed lots of occurrences in input processing for the dummy file that has all the screens etc that it uses to access the 'main data file' was full of 'write' statements....keeping in mind, this particular code was written before my time and has worked flawlessly for many years</div>
<div>So recently it was noticed that two people could pull up the same record when in the 'dummy file' and only the person who first accessed the record - those changes would reflect, but not the 2nd person....so I made a copy of the input processing table....then went in and commented out all the 'write' statements in the input processing - now it's once again working as it was designed and I do in fact get the 'Waiting for .... record to be unlocked' message (as I should be getting and as I have been getting for many years)</div>
<div>So I guess my question is, where/what is the potential of commenting out all the 'write' statements? I'm trying to decipher through the filepro help menu when a 'write' is needed</div><div>The 'dummy' file that is used with multiple screens and does the protected lookups to the 'main' data file is used by the majority of our staff here - and they in fact will pull up records in various ways and make changes to data that is in the main data file......</div>
<div>When can I do a 'write' or should I etc if they're doing protected lookups, etc?</div><div>Just need some guidance I guess on when a 'write' is needed - without 'breaking' what's working again</div>
<div>Thanks for any input</div><div> </div><div>Scott</div><div>PDM</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 17, 2014 at 12:18 PM, <a href="mailto:scooter6@gmail.com">scooter6@gmail.com</a> <span dir="ltr"><<a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Well, there aren't 2 lookups per se I'm using when doing this.......</div><div>If I do DIRECTLY to the main data file through IUA, and then try to pull that same acct up in the input processing of the 'dummy' file that does all the protected lookups, I get the</div>
<div>'Wating for record to be unlocked...' message....</div><div>If I reverse that, and pull up the record in the 'dummy' file that does all the protected lookups FIRST, and then use IUA directly to the data file, I can access the record with no problem?</div>
<div>Hope that makes sense.....</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 16, 2014 at 3:46 PM, Kenneth Brody <span dir="ltr"><<a href="mailto:kenbrody@spamcop.net" target="_blank">kenbrody@spamcop.net</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div>On 4/16/2014 3:07 PM, <a href="mailto:scooter6@gmail.com" target="_blank">scooter6@gmail.com</a> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
Okay - after some more digging.....if I pull a record up directly in the<br>
filePro file itself and am in update mode...and then try to pull the<br>
account up in the processing that does all the lookups and protected<br>
lookups, I get 'Wating for 'mainfile' record xxxxxx to be unlocked'<br>
But, if I pull up the record in the processing that does all the lookups<br>
and what the employees use to access the main file, it lets me pull it up<br>
with no problem?<br>
</blockquote>
<br></div>
What's difference about the lookup in the prc that waits for the lock, and the one that doesn't wait?<span><font color="#888888"><br>
<br>
-- <br>
Kenneth Brody<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>