I am more interested in doing this "DELETE" in file #2. I only have 20 records there. And I may want do to that a time or two, while I work with UPDATE^DIE transporting records from an older system
What should I expect? thurman > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:hardhats- > [EMAIL PROTECTED] On Behalf Of Greg Woodhouse > Sent: Monday, June 27, 2005 4:55 PM > To: hardhats-members@lists.sourceforge.net > Subject: RE: [Hardhats-members] UPDATE^DIE > > In this case, my presumption is that th entries were created during > testing of the upload procedure and nothing has been linked to them > yet. Normally, of course, entries should never be deleted from file > 200, but you could try scanning through all the file pointing to 200 > and deleting the dangling pointers to see what happens, if you wish. > > --- Kevin Toppenberg <[EMAIL PROTECTED]> wrote: > > > Well, its a situation of waiting a long time, or > > having a database full of dangling pointers. I would > > say to answer "YES" and leave the machine to run for > > the night. > > > > Kevin > > > > > > --- Greg Woodhouse <[EMAIL PROTECTED]> > > wrote: > > > > > Just remember to say "NO" when Fileman asks you if > > > it should delete or > > > re-point dangling pointers, or you could be waiting > > > a long time. > > > Usually, I recommend saying "YES", but it in this > > > case, it wouldn't be > > > a good idea. > > > > > > --- Cameron Schlehuber <[EMAIL PROTECTED]> > > > wrote: > > > > > > > If you haven't been doing anything that would have > > > other entries in > > > > the > > > > hundreds of other files that point to file 200, > > > you should be able to > > > > safely > > > > remove the entries by using FileMan's EDIT FILE > > > option under the > > > > UTILITY > > > > FUNCTIONS menu. Select file 200 and at the NAME > > > prompt enter the "@" > > > > and > > > > opt to delete the contents and keep the DD. > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > > > > > > > > [mailto:[EMAIL PROTECTED] > > > On Behalf Of > > > > Theriot, > > > > Derek > > > > Sent: Monday, June 27, 2005 2:02 PM > > > > To: hardhats-members@lists.sourceforge.net > > > > Subject: RE: [Hardhats-members] UPDATE^DIE > > > > > > > > > > > > > > > > Thanks for all the help. I've been making some > > > good progress. Now I > > > > am at > > > > the point where I would like to reuse the input > > > file I have. Is > > > > there any > > > > way to start over with no data in file 200 or > > > would I need to do a > > > > complete > > > > reinstall? > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > > > > > > > > [mailto:[EMAIL PROTECTED] > > > On Behalf Of > > > > [EMAIL PROTECTED] > > > > > > > > Sent: Friday, June 24, 2005 11:27 AM > > > > To: hardhats-members@lists.sourceforge.net > > > > Subject: Re: [Hardhats-members] UPDATE^DIE > > > > > > > > The UPDATE^DIE call which is the subject of this > > > thread, is a pretty > > > > good > > > > way to do it. You would use an "@" as the stored > > > value for the ACCESS > > > > CODE > > > > field ( field #2 on file #200 ). > > > > > > > > > > > > > > > > > Is there a "proper" way to delete the access > > > code from the user to > > > > ensure > > > > > that the old code gets moved to AOLD? > > > > > > > > > > > > > > > > > > > > _____ > > > > > > > > > > From: > > > [EMAIL PROTECTED] > > > > > > > > > > [mailto:[EMAIL PROTECTED] > > > On Behalf Of > > > > James > > > > > Gray > > > > > Sent: Friday, June 24, 2005 10:25 AM > > > > > To: hardhats-members@lists.sourceforge.net > > > > > Subject: Re: [Hardhats-members] UPDATE^DIE > > > > > > > > > > > > > > > > > > > > Don't delete the "A" X-ref. It also applies to > > > all of the existing > > > > access > > > > > > > > > codes. When you delete the access code for a > > > person in file 200 > > > > that will > > > > > > > > > delete the entry for that access code from X-ref > > > A and move it to > > > > the > > > > "AOLD" > > > > > X-ref. > > > > > > > > > > > > > > > > > > > > Jim Gray > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > From: Theriot, Derek <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > To: hardhats-members@lists.sourceforge.net > > > > > <mailto:hardhats-members@lists.sourceforge.net> > > > > > > > > > > > > > Sent: Friday, June 24, 2005 8:58 AM > > > > > > > > > > Subject: RE: [Hardhats-members] UPDATE^DIE > > > > > > > > > > > > > > > > > > > > Is there a way to delete the scrambled password > > > before deleting the > > > > "A" > > > > > x-ref? > > > > > > > > > > -----Original Message----- > > > > > From: > > > [EMAIL PROTECTED] > > > > > > > > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > [mailto:[EMAIL PROTECTED] > > > > > > > > > > > > > <mailto:[EMAIL PROTECTED]> > > > ] On Behalf > > > > Of > > > > > [EMAIL PROTECTED] > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > Sent: Friday, June 24, 2005 9:10 AM > > > > > To: hardhats-members@lists.sourceforge.net > > > > > <mailto:hardhats-members@lists.sourceforge.net> > > > > > > > > Subject: Re: [Hardhats-members] UPDATE^DIE > > > > > > > > > > The "A" crossref is used to look up a scrambled > > > password, so if you > > > > delete > > > > > > > > > it, then you can't find the record that had that > > > scrambled > > > > password. > > > > > I would also consider changing the access code > > > stored in the > > > > database. > > > > > (ie: > > > > > ^VA(200,D0,0)=(#.01) NAME [1F] ^ (#1) INITIAL > > > [2F] ^ (#2) ACCESS > > > > CODE[3F] > > > > > > > > > > > > > > or $P(^VA(200,DUZ,0),"^",3) > > > > > > > > > > if you or someone else later want to re-index > > > the field, or answer > > > > "all" > > > > > at the proper prompt, these "not so old" access > > > codes could come > > > > back and > > > > > bother you. > > > > > > > > > > David > > > > > > > > > > > > > > > > > > > > > So deleting the "A" x-ref for a "not so old" > > > account is the same > > > > as > > > > > deleting > > > > > > the "AOLD" x-ref for an account that's been > > > logged as "old"? > > > > > > > > > > > > > > > > > > > > > > > > _____ > > > > > > > > > > > > From: > > > [EMAIL PROTECTED] > > > > > > > > > [mailto:[EMAIL PROTECTED] > > > > > > > > > > > > > <mailto:[EMAIL PROTECTED]> > > === message truncated === > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration > > Strategies > > from IBM. Find simple to follow Roadmaps, straightforward articles, > > informative Webcasts and more! Get everything you need to get up to > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > _______________________________________________ > > Hardhats-members mailing list > > Hardhats-members@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > > > > > === > Gregory Woodhouse <[EMAIL PROTECTED]> > Health Systems Design & Development > "Design quality doesn't ensure success, but design failure can ensure > failure." > > --Kent Beck > > > > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Hardhats-members mailing list > Hardhats-members@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
