That should work. I was working on an automated/scripting system. So for my final system, I just ran the script.
Kevin --- "Theriot, Derek" <[EMAIL PROTECTED]> wrote: > Sounds like it would be "cleaner" to do the > reinstall. I haven't had to do > this yet. How do I go about this? Do I just copy > over the cache.dat file > with a fresh one and go through the install > instructions again? > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Kevin > Toppenberg > Sent: Monday, June 27, 2005 5:40 PM > To: hardhats-members@lists.sourceforge.net > Subject: RE: [Hardhats-members] UPDATE^DIE > > I went through 3 generations of installs, building > up > to my production environment. It was less stressful > that way. Its usually faster with each subsequent > install. > > But you are not supposed to delete entries in file > 200. You could get around that, but it might cause > unexpected crashes later on. > > Kevin > > > --- "Theriot, Derek" <[EMAIL PROTECTED]> wrote: > > > 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]> > > ] On Behalf Of > > Cameron > > > > > > > Schlehuber > > > > Sent: Thursday, June 23, 2005 5:02 PM > > > > To: hardhats-members@lists.sourceforge.net > > > > Subject: RE: [Hardhats-members] UPDATE^DIE > > > > > > > > > > > > > > > > Under Manage User File, use the Purge Log of > Old > > Access and Verify Codes > > > > > > [XUSERAOLD] (of course, if the person's code > > hasn't been logged as > > "old" > > > > yet, it will still be in the "A" x-ref.) > > > > > > > > > > > > > > > > -----Original Message----- > === message truncated === ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.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
