One of the best early global file structure docs I've read was written in Finland (User's Technical Manual) by Jukka Kiskimies. I still keep it within reach. I guess now I have to keep the FDA array doc handy.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ormsby, Skip Sent: Tuesday, October 05, 2004 9:57 AM To: [EMAIL PROTECTED] Subject: RE: [Hardhats-members] ?? FILE^DIE bug ?? Your welcome Kevin. Kevin, I too didn't retain that, but I, having been around FileMan when Word Processing fields were introduced, knew that Word Processing fields, although they look and feel like a multiple, they are not.. Kevin of all of the documentation that could be printed, there are two bits I have printed and keep handy all of the time. The first is FileMan Global File Structure and the second is the FDA array. --Skip -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg Sent: Tuesday, October 05, 2004 12:00 PM To: [EMAIL PROTECTED] Subject: RE: [Hardhats-members] ?? FILE^DIE bug ?? Skip, Thanks. That explains a lot. I have tried to read that section of the fileman manual, but I guess I didn't retain that part. It seems like the fileman code should be able to protect itself agains an error like mine, but maybe it is depending on an error trap set elsewhere. Thanks again, Kevin --- "Ormsby, Skip" <[EMAIL PROTECTED]> wrote: > Hi Kevin, et. al. > > The problem you are having is that you are not setting up your FDA > array properly. The following is a brief excerpt from the FDA > documentation for VALUE: > > "The values for word processing fields are stored in the FDA > differently. Instead of setting the node equal to the actual value, > set it equal to the root of an array (local or global) that holds the > data. > " > > So using your example Kevin: > Select OPTION: INQUIRE TO FILE ENTRIES > > > > OUTPUT FROM WHAT FILE: KERNEL SYSTEM PARAMETERS// > Select KERNEL SYSTEM PARAMETERS DOMAIN NAME: > <domain name> > ANOTHER ONE: > STANDARD CAPTIONED OUTPUT? Yes// N (No) FIRST PRINT FIELD: 240 INTRO > MESSAGE > (word-processing) > THEN PRINT FIELD: > Heading (S/C): KERNEL SYSTEM PARAMETERS LIST Replace > DEVICE: SYSTEM Right Margin: 80// > KERNEL SYSTEM PARAMETERS LIST OCT > 5,2004 05:50 > PAGE 1 > INTRO TEXT > ------------------------------------------------------------------------ > -------- > > S INTRO="" > S INTRO(1)="Welcome to OpenVistA EMR" > S FDA(8989.3,"1,",240)="INTRO" > S FLAGS="KE" > D FILE^DIE(FLAGS,"FDA","ZERR") > > Select OPTION: INQUIRE TO FILE ENTRIES > > > > OUTPUT FROM WHAT FILE: KERNEL SYSTEM PARAMETERS// > Select KERNEL SYSTEM PARAMETERS DOMAIN NAME: <a > domain name> > ANOTHER ONE: > STANDARD CAPTIONED OUTPUT? Yes// N (No) > FIRST PRINT FIELD: INTRO MESSAGE > (word-processing) > THEN PRINT FIELD: > Heading (S/C): KERNEL SYSTEM PARAMETERS LIST Replace > DEVICE: SYSTEM Right Margin: 80// > KERNEL SYSTEM PARAMETERS LIST OCT > 5,2004 05:54 > PAGE 1 > INTRO TEXT > ------------------------------------------------------------------------ > -------- > > Welcome to OpenVistA EMR > > Hope this helps explain the "how to". > > --Skip > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Kevin > Toppenberg > Sent: Monday, October 04, 2004 8:05 PM > To: [EMAIL PROTECTED] > Subject: RE: [Hardhats-members] ?? FILE^DIE bug ?? > > Fil, > > I could do that, but then I'd have to test myself if the user is > trying to upload to a standard field, or a WP field. It looks to me > like the standard FILE^DIE is making this test (and as such I could > copy that code for my own use). I wish it was working properly. > > But if I can't I use this function as a work-around. > > Thanks > > Kevin. > > P.S., do you think it IS a bug? > > --- "Beza, Fil" <[EMAIL PROTECTED]> wrote: > > > Why not try > > > > WP^DIE( ): Word Processing Filer > > This procedure files a single word processing > field. > > > > > > Format > > WP^DIE(FILE,IENS,FIELD,FLAGS,wp_root,msg_root) > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > > On Behalf Of Kevin > > Toppenberg > > Sent: Monday, October 04, 2004 3:17 PM > > To: Hardhats Sourceforge > > Subject: [Hardhats-members] ?? FILE^DIE bug ?? > > > > I am having an unusual error when using FILE^DIE > to upload a value > > into a word processing field. The execution just > drops out and exits > > back to the command line when I call the function. > In these > > situations, it is more likely my problem than the > API's, but I can't > > figure out the issue. > > Here is my input data: > > > > FDA structure > > +-8989.3 > > | > > +--"1," > > | > > +--".01"="TMG.TMGDOMAIN.COM" > > | > > +--"240"="Welcome to OpenVistA EMR" > > > > Flags="KE" > > MsgG=(not yet defined) > > > > I call FILE^DIE(Flags,"FDA","Msg") which results > in the following > > series of calls: > > --> FILEX^DIEF > > --> D DRIVER > > --> D PUTDATA^DIEF1 > > --> D PUTWP^DIEFW(DIEFFLAG,DIEFNVAL,DIEFNODE) > > in this case: ==> D PUTWP^DIEFW("KE","welcome > to OpenVistA EMR > > System","^XTV(8989.3,1,""INTRO"")") > > I then come to a consistent crash at the following > point (Note the > > '==>' > > on the 3rd line): > > ----------------------------------------------- > > PUTWP(DIEFWPFL,DIEFTSRC,DIEFNODE) ; > > N BEGIN > > I "@"[DIEFTSRC K @DIEFNODE Q > > ==> I '($D(@DIEFTSRC)\10) D > > BLD^DIALOG(305,DIEFTSRC,DIEFTSRC) Q > > I $G(DIEFWPFL)'["A" S BEGIN=1 K @DIEFNODE > > E S BEGIN=$$NUMLNS(DIEFNODE)+1 K:BEGIN=1 > @DIEFNODE > > I $D(@DIEFTSRC@($O(@DIEFTSRC@(0)),0))#2 S > DIEFWPFL=$G(DIEFWPFL)_"Z" > > N LINECNT,INLINE S INLINE=0 > > F LINECNT=BEGIN:1 S INLINE=$O(@DIEFTSRC@(INLINE)) > > Q:INLINE'=+$P(INLINE,"E") D > > . I $G(DIEFWPFL)'["Z" S > > @DIEFNODE@(LINECNT,0)=$G(@DIEFTSRC@(INLINE)) > > . E S > > @DIEFNODE@(LINECNT,0)=$G(@DIEFTSRC@(INLINE,0)) > > S LINECNT=LINECNT-1 > > S @DIEFNODE@(0)=U_U_LINECNT_U_LINECNT_U_DT > > Q > > ---------------------------------------------- > > > > What's strange here is that DIEFTSRC="Welcome to > OpenVistA EMR System" > > so @DIEFTSRC has no meaning. > > > > Notice also that the calling parameters are: > > > > D PUTWP^DIEFW(DIEFFLAG,DIEFNVAL,DIEFNODE) ... > found in DIEF1.m > > > > but the PUTWP function expects these parameters: > > > > PUTWP(DIEFWPFL,DIEFTSRC,DIEFNODE) .. declared in > DIEFW.m > > > > It seems to me that the middle parameter (in my > case the string > > "Welcome...") is passed as a string input value, > but === message truncated === __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members
