LOL.  Ahh, a good challenge is fun to conqueror.

And yes I have completed my code.  I'll be happy to share it if anyone
is interested.  I scans through all files that point to the specified
file, and looks for instances of the specified record.

I then stores all such references in an array like this:
Array(File#,IEN,FullGlobalRefOfEntry,piece,IENS)

The programmer should then be able to order through this and perform
whatever action is wanted.... either via database API calls (utilizing
the IENS), or via direct SETS (bypassing triggers/safeguards etc
etc.).

It wouldn't be that much trouble to change this array into a format
that fileman uses to delete or change all such pointers.  I.e. after
deleting a record it asks "DO YOU WANT TO UPDATE ALL POINTERS TO THIS
RECORD (WHICH MIGHT TAKE AWHILE)?"

I searched for all references to my name in all files.... Wow!  I
think there are 6 million or something.  I imported a bunch of old
progress notes, and also did all the patient registration stuff..

Kevin




On 11/17/05, Greg Woodhouse <[EMAIL PROTECTED]> wrote:
> My guess is that the complexity of the problem will make Kevin try all the
> harder!
>
> It is difficult, and only one reason why working with file definitions
> programmatically is difficult. Personally, I think DINUM is a "mis-feature",
> but it isn't at all hard to see why it was included in Fileman., as it
> provides a natural way to model "is-a" relationships, and it simplifies
> programming in raw MUMPS allowing programmers to check to see if a record is
> present with a simple $DATA.
>
> "Holloway, Thomas (EDS)" <[EMAIL PROTECTED]> wrote:
> Kevin,
> I think you are beginning to see a part of the reason why the tool
> that you are seeking doesn't exist. It's not only complicated but may,
> in the end, require human decision making at each pointer level to
> decide whether to repoint and, if so, where to repoint. The larger
> factor, I believe, is that this functionality is not generally needed in
> a production database. You are starting from scratch, so to speak, but
> with a set of files that contain data you don't need/want. In a live
> hospital database they would never be deleting drugs (or other pointed
> to values) since there is a need to retain historical accuracy.
>
> tjh


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to