Auto Exit

[Richard Kreiss]

Nancy,

Wouldn't your suggestion work using a qualifier.  This would insure that the two file always had matching maps and screens.

Richard Kreiss

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Nancy Palmquist
> Sent: Wednesday, December 04, 2013 3:22 PM
> To: filepro-list at lists.celestial.com
> Subject: Re: Auto Exit
> 
> Wayne,
> 
> Your question has been discussed many many times over the years. How can
> you control the user and make sure they do not leave records and files
> locked.
> 
> I have never seen a great solution, however, I can propose an idea.
> 
> For my systems that have a large number of users and I need to make sure
> they do not block functions on a data file, I do the following.
> 
> I setup all the programming and data entry in a work file.  The work file pulls in
> the data from the real file, does the appropriate functions and then writes the
> record back to the real file.
> 
> You could make a copy of the map and programming from your Real File to a
> Work file.  Just add logic to take the new added records and write them to the
> real file when you save the record.  Problem solved, because the work file
> does not have any real data stored, you can reset it to zero once in a while.
> (Do not DELETE the records as you add them.  I find that will corrupt the file
> over time.  It works better to just add records and reset the file to zero once a
> week or so.)
> 
> To manage updates to data, it is the same idea, grab the record you want
> updated, fix it and when you save it write it back to the Real File.
> Don't forget to use the proper record locking in the lookups.  You might add a
> field in the Real File to mark when you are updating the record.
> So you do not have to leave the record locked for a long time _ again they
> might walk away and leave it locked _ just mark the field and check to see if
> the field is marked before you let someone else update that record.
> 
> You get the idea.
> 
> I hope this helps.  I know it is just a concept but it should give you a way to
> proceed.
> Nancy
> 
> On 11/25/2013 6:12 AM, SmittyUSN1 wrote:
> > I was hoping the list could give me some ideas on how to keep a user from
> leaving their workstation in a blank record.  I exit them back to a menu after
> they SAVE a record,  this is happening when they ADD a record, then leave.
> >
> > I would like to CLOSE the open record and EXIT back to the menu in  XX
> amount of time (10 minutes) after NO activity from the user.   I have toyed
> with TIME now, but not getting anywere.
> >
> > Windows 7,  filePro 5.0.9  Network
> >
> > Thanks ahead of time,
> >
> > Wayne Smith
> > Port Orange, Florida
> >
> > -------------- next part -------------- An HTML attachment was
> > scrubbed...
> > URL:
> > http://mailman.celestial.com/pipermail/filepro-list/attachments/201311
> > 25/947bf04c/attachment.html
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > Subscribe/Unsubscribe/Subscription Changes
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> 
> --
> Nancy Palmquist
> Owner
> Virtual Software Systems - www.vss3.com
> (412) 835-9417
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list