<div> Can someone point me in the direction of using qualifiers?</div>
<div> I'm a little vague on how I would set that up.</div>
<div> </div>
<div> Currently, we have over 4000 clients - but only one that currently wants to </div>
<div> be able to VIEW their records - they will NOT be permitted to change a single</div>
<div> thing.....so, my plan using @menu and "drop" was to add @entsel processing</div>
<div> with just "V" to view and once they view the record, they will also be able to</div>
<div> lookup to another file to VIEW notes we have on their records...but that's it</div>
<div> </div>
<div> Until I find a bigger, permanent solution I will probably copy their records each</div>
<div> night to a "dummy" file and just build a view screen...that's easiest at this point</div>
<div> But I will continue to find a smoother way to do this as there are other clients</div>
<div> that will be forthcoming I'm told that will want this same functionality.</div>
<div> </div>
<div> Each "client number" can only have a maximum of 9999 records.</div>
<div> i.e. 1234-0001 thru 1234-9999 -- once they have more records than that, they</div>
<div> are assigned another client number, etc. Not an ideal scenario but this is how</div>
<div> it was built a long time ago...now we're getting more and more business and</div>
<div> several clients have exceeded 9999 records so we've had to add a second and</div>
<div> sometimes third client number - but that's another story in itself and something</div>
<div> that will require a major overhaul.</div>
<div> </div>
<div> Thanks for everyone's suggestions - I'm sure I'll/we'll find a way to make this work</div>
<div> </div>
<div> For now, I'm still plugging away</div>
<div> </div>
<div> Scott</div>
<div><br><br> </div>
<div class="gmail_quote">On Thu, Sep 3, 2009 at 9:19 AM, Tom Aldridge <span dir="ltr"><<a href="mailto:toma@aldridgeinc.com">toma@aldridgeinc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im"><a href="mailto:scooter6@gmail.com">scooter6@gmail.com</a> wrote:<br><br>> I only have 1 client at this time that I'm building this for, but it will<br>> be used more<br>> and more as I have heard we have several clients that have requested this<br>
> functionality......<br>><br>> But, for this project, just 1 client and they will have about 600 records<br>> in<br>> the "browse lookup" file out of approx 550,000 so it does take a bit to<br>
> load<br>> just their records based on the 'drop' processing I'm using.....<br><br></div>Hi. Are you the original poster on this? Anyway... not to just beat the<br>drum over again on the qualifier thing, but now that I know you<br>
presently have one client who wants this and more on the way, I think<br>maintaining the records at all times in the qualified files (vs the<br>original suggestion to copy to the qualifier on the fly) would be nice<br>and fast and clean. Browse processing is great for a many things<br>
including dropping records, but as you know, not so when it comes to<br>dropping lots and lots of records.... because it's reading every record<br>and making a drop decision vs using an index.<br><br>Depending on what you anticipate for the number of future clients vs any<br>
sort of filePro limitations to qualifiers, you could have each client<br>work out of THEIR qualifier, and if you need to combine the various<br>client records back into the main file, then do so as they create,<br>update or delete their qualified records.<br>
<br>What do you think of that?<br><font color="#888888"><br>Tom Aldridge<br></font>
<div>
<div></div>
<div class="h5">_______________________________________________<br>Filepro-list mailing list<br><a href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a><br><a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
</div></div></blockquote></div><br>