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