IBDEHELP ; ALB/ISC - ENCOUNTER FORM UTILITIES - INSTRUCTIONS FOR EXECUTING DIFROM ;AUG 16, 1993
;;3.0;AUTOMATED INFO COLLECTION SYS;;APR 24, 1997
HELP ;
N LINE,IBARY,IBHDRRTN,CNT
S IBHDRRTN="D HDR^IBDEHELP"
S CNT=0
S IBARY="^TMP(""IBDF"",$J,""IMP/EXP HELP"")"
K @IBARY
F S LINE=$P($T(LINES+CNT),";;",2) Q:LINE="" D
.S CNT=CNT+1
.S @IBARY@(CNT,0)=LINE
S $P(@IBARY@(0),"^",4)=CNT
D EN^VALM("IBDE TEXT DISPLAY")
K @IBARY
S VALMBCK="R"
Q
HDR ;
S VALMHDR(1)="HELP for the IMPORT/EXPORT UTILITY"
Q
;
LINES ;;The initial install of the Encounter Form Utilities at your site
;;included a toolkit of forms and blocks. The ONLY SAFE METHOD for
;;transferring additional forms and blocks between sites is through this
;;IMPORT/EXPORT UTILITY.
;;
;;The IMPORT/EXPORT UTILITY includes a set of files that are nearly
;;identical to the files used by the ENCOUNTER FORM UTILTIES to contain
;;the form descriptions. These import/export files constitute a WORK
;;SPACE in which forms and blocks can be safely exported (to other sites)
;;and imported (from other sites to your own).
;;
;;You should have a PACKAGE entry for the IMPORT/EXPORT UTILITY already
;;set up. The files listed should be in the range 358 to 358.91.
;;The package entry is named IB ENCOUNTER FORM IMP/EXP, and the prefix
;;is IBDE. The package entry is necessary to accomplish EXPORT.
;;
;;
;;TO IMPORT:
;;
;; 1) The other site must have prepared a set of inits, using this
;; utility, that contain the forms and toolkit blocks they want to
;; transfer.
;;
;; 2) The work space MUST NOT ALREADY CONTAIN any forms or blocks that
;; you want to keep. First decide what you want to do with anything
;; that is already in the workspace. The work space will be cleared
;; before the inits are executed, so anything there will be lost.
;;
;; 3) You must execute the inits, using this this utility, by choosing
;; the action RUN INITS. The init should normally be named IBDEINIT.
;;
;; 4) The work space should now contain forms and toolkit blocks. You
;; can choose which ones you want, then choose the action IMPORT
;; ENTRY to actually make the form or block available for use. The
;; forms can not be viewed while in the work space, but you can view
;; the IMPORT/EXP NOTES.
;;
;;TO EXPORT:
;;
;; 0) Only users with PROGRAMMER ACCESS can export.
;;
;; 1) First clear the work space of anything you do not want to export.
;;
;; 2) Then add any forms or blocks to the work space that you do want
;; to export.
;;
;; 3) Add EXPORT/IMPORT NOTES to each entry you add to the work space.
;; You must accuratly describe the form for the site that you are
;; exporting it to. They will be able to view the notes, but they
;; will not be able to view the form itself until they import it.
;;
;; 4) Then, through the DIFROM action that is part of this utility,
;; create the inits that will be sent to the other site.
;;
;; 5) Send the inits to the other site.
--- Routine Detail --- with STRUCTURED ROUTINE LISTING ---[H[J[2J[HIBDEHELP 3162 printed Apr 09, 2024@21:24:45 Page 2
IBDEHELP ; ALB/ISC - ENCOUNTER FORM UTILITIES - INSTRUCTIONS FOR EXECUTING DIFROM ;AUG 16, 1993
+1 ;;3.0;AUTOMATED INFO COLLECTION SYS;;APR 24, 1997
HELP ;
+1 NEW LINE,IBARY,IBHDRRTN,CNT
+2 SET IBHDRRTN="D HDR^IBDEHELP"
+3 SET CNT=0
+4 SET IBARY="^TMP(""IBDF"",$J,""IMP/EXP HELP"")"
+5 KILL @IBARY
+6 FOR
SET LINE=$PIECE($TEXT(LINES+CNT),";;",2)
if LINE=""
QUIT
Begin DoDot:1
+7 SET CNT=CNT+1
+8 SET @IBARY@(CNT,0)=LINE
End DoDot:1
+9 SET $PIECE(@IBARY@(0),"^",4)=CNT
+10 DO EN^VALM("IBDE TEXT DISPLAY")
+11 KILL @IBARY
+12 SET VALMBCK="R"
+13 QUIT
HDR ;
+1 SET VALMHDR(1)="HELP for the IMPORT/EXPORT UTILITY"
+2 QUIT
+3 ;
LINES ;;The initial install of the Encounter Form Utilities at your site
+1 ;;included a toolkit of forms and blocks. The ONLY SAFE METHOD for
+2 ;;transferring additional forms and blocks between sites is through this
+3 ;;IMPORT/EXPORT UTILITY.
+4 ;;
+5 ;;The IMPORT/EXPORT UTILITY includes a set of files that are nearly
+6 ;;identical to the files used by the ENCOUNTER FORM UTILTIES to contain
+7 ;;the form descriptions. These import/export files constitute a WORK
+8 ;;SPACE in which forms and blocks can be safely exported (to other sites)
+9 ;;and imported (from other sites to your own).
+10 ;;
+11 ;;You should have a PACKAGE entry for the IMPORT/EXPORT UTILITY already
+12 ;;set up. The files listed should be in the range 358 to 358.91.
+13 ;;The package entry is named IB ENCOUNTER FORM IMP/EXP, and the prefix
+14 ;;is IBDE. The package entry is necessary to accomplish EXPORT.
+15 ;;
+16 ;;
+17 ;;TO IMPORT:
+18 ;;
+19 ;; 1) The other site must have prepared a set of inits, using this
+20 ;; utility, that contain the forms and toolkit blocks they want to
+21 ;; transfer.
+22 ;;
+23 ;; 2) The work space MUST NOT ALREADY CONTAIN any forms or blocks that
+24 ;; you want to keep. First decide what you want to do with anything
+25 ;; that is already in the workspace. The work space will be cleared
+26 ;; before the inits are executed, so anything there will be lost.
+27 ;;
+28 ;; 3) You must execute the inits, using this this utility, by choosing
+29 ;; the action RUN INITS. The init should normally be named IBDEINIT.
+30 ;;
+31 ;; 4) The work space should now contain forms and toolkit blocks. You
+32 ;; can choose which ones you want, then choose the action IMPORT
+33 ;; ENTRY to actually make the form or block available for use. The
+34 ;; forms can not be viewed while in the work space, but you can view
+35 ;; the IMPORT/EXP NOTES.
+36 ;;
+37 ;;TO EXPORT:
+38 ;;
+39 ;; 0) Only users with PROGRAMMER ACCESS can export.
+40 ;;
+41 ;; 1) First clear the work space of anything you do not want to export.
+42 ;;
+43 ;; 2) Then add any forms or blocks to the work space that you do want
+44 ;; to export.
+45 ;;
+46 ;; 3) Add EXPORT/IMPORT NOTES to each entry you add to the work space.
+47 ;; You must accuratly describe the form for the site that you are
+48 ;; exporting it to. They will be able to view the notes, but they
+49 ;; will not be able to view the form itself until they import it.
+50 ;;
+51 ;; 4) Then, through the DIFROM action that is part of this utility,
+52 ;; create the inits that will be sent to the other site.
+53 ;;
+54 ;; 5) Send the inits to the other site.
