1 | English French Notes Complete/Exclude
|
---|
2 | of table
|
---|
3 | INDEX PRIMARY KEY: COLUMN ELEMENT INSERT FAILED
|
---|
4 | INDEX PRIMARY KEY: COLUMN INSERT FAILED
|
---|
5 | INDEX PRIMARY KEY: TABLE ELEMENT INSERT FAILED
|
---|
6 | FOREIGN KEY: NO POINTED-TO FILE IN SPECIFIER
|
---|
7 | FOREIGN KEY: NO TABLE FOR POINTED-TO FILE
|
---|
8 | FOREIGN KEY: NO PRIMARY KEY TABLE ELEMENT
|
---|
9 | FOREIGN KEY: NO ASSOCIATED PRIMARY KEY
|
---|
10 | Foreign key to
|
---|
11 | FOREIGN KEY: TABLE ELEMENT INSERT FAILED
|
---|
12 | FOREIGN KEY: COLUMN ELEMENT INSERT FAILED
|
---|
13 | Foreign key to ancestor
|
---|
14 | FOREIGN KEY: ANCESTOR FOREIGN KEY INSERT FAILED
|
---|
15 | FOREIGN KEY: NO POINTED-TO COLUMN AT LEVEL
|
---|
16 | FOREIGN KEY: NO ANCESTOR PRIMARY KEY
|
---|
17 | FOREIGN KEY: ANCESTOR FOREIGN KEY COLUMN INSERT FAILED
|
---|
18 | INDEX: MISSING DATA DICTIONARY DATA
|
---|
19 | INDEX: IRREGULAR FORMAT
|
---|
20 | INDEX: NO ASSOCIATED COLUMN RECORD
|
---|
21 | Index of
|
---|
22 | INDEX: TABLE INSERT FAILED
|
---|
23 | INDEX: TABLE DOMAIN INSERT FAILED
|
---|
24 | Primary key header for
|
---|
25 | INDEX: PRIMARY KEY ELEMENT INSERT FAILED
|
---|
26 | Index Primary Key #
|
---|
27 | INDEX: COLUMN ELEMENT INSERT FAILED
|
---|
28 | INDEX: COLUMN INSERT FAILED
|
---|
29 | INDEX: PRIMARY KEY INSERT FAILED
|
---|
30 | NO POINTERS
|
---|
31 | You need 'Read' access to one SQLI file to run this report.
|
---|
32 | It is file 1.5212.
|
---|
33 | Contact your system manager to be granted single file access.
|
---|
34 | TABLES POINTING TO
|
---|
35 | FROM TABLE:
|
---|
36 | VIA FOREIGN KEY:
|
---|
37 | TABLES POINTED-TO BY
|
---|
38 | TO TABLE:
|
---|
39 | VA FOREIGN KEY:
|
---|
40 | DMSQ(
|
---|
41 | SQLI TABLE COUNT (EXCLUDING INDEX-TYPE)
|
---|
42 | REGULAR TABLES
|
---|
43 | SQLI COLUMN COUNT FOR ALL TABLES
|
---|
44 | SQLI INDEX COUNT (INDEX-TYPE TABLES)
|
---|
45 | SQLI TABLE ELEMENT TYPE TOTALS
|
---|
46 | TYPE=
|
---|
47 | SQLI COLUMN TOTALS BY TABLE
|
---|
48 | TABLE:
|
---|
49 | SQLI TABLES SORTED BY TOTAL COLUMNS
|
---|
50 | COLUMN COUNT:
|
---|
51 | SQLI COLUMN COUNT FOR REGULAR TABLES (EXCLUDING INDEXES)
|
---|
52 | SQLI COLUMN COUNT, REGULAR TABLES, EXCLUDING TABLE_IDS
|
---|
53 | SQLI COLUMN COUNT BY DOMAIN (REGULAR TABLES, EXCLUDING TABLE_IDS)
|
---|
54 | DOMAIN=
|
---|
55 | You need 'Read' access to four SQLI files to run this report.
|
---|
56 | They are files 1.5211, 1.5212, 1.5214, and 1.5216.
|
---|
57 | Starting File Number
|
---|
58 | Enter the number of the file, e.g. 200 or 1.5215
|
---|
59 | SQLI table not found.
|
---|
60 | Ending File Number
|
---|
61 | Optionally enter a larger number for a range, e.g. 1.5217
|
---|
62 | There isn't a table for the file number you've entered.
|
---|
63 | (The highest possible number is
|
---|
64 | Enter a LARGER number to get a range.
|
---|
65 | The highest possible number here is
|
---|
66 | SQLI PROJECTION OF FIELDS AS COLUMNS
|
---|
67 | INTERNAL(#4);C1;S;X,.01;C15;X,7;C15;X,5;C42;X,
|
---|
68 | OF_DATA_TYPE:
|
---|
69 | OF_EXT_EXPR:
|
---|
70 | DM_DATA_TYPE:
|
---|
71 | DM_WIDTH/DM_SCALE:
|
---|
72 | SQLI TABLE NAME:
|
---|
73 | FILE NUMBER:
|
---|
74 | INTERNAL(#6);
|
---|
75 | FILE#
|
---|
76 | FILEMAN FILE NAME
|
---|
77 | SQLI TABLE NAME
|
---|
78 | SQLI TABLES BY FILE NUMBER
|
---|
79 | (1) SELF Tables with Self-referential Pointers
|
---|
80 | (2) UP Tables with Upward Links
|
---|
81 | (3) DOWN Tables Linked from Below
|
---|
82 | (4) OUT Tables Pointing Outward
|
---|
83 | (5) IN Tables with Incoming Pointers
|
---|
84 | (9) QUIT Exit this Menu
|
---|
85 | Select a report:
|
---|
86 | This can take 1-2 minutes. Continue
|
---|
87 | These reports show counts. Or would you prefer details
|
---|
88 | WORD_PROCESSING
|
---|
89 | Please wait...
|
---|
90 | SQLI TABLE POINTER COUNTS
|
---|
91 | FILE/SUBFILE:
|
---|
92 | WORD-PROCESSING TABLE?
|
---|
93 | SELF-REFERENTIAL POINTERS:
|
---|
94 | POINTERS DOWNWARD TO THIS SUBFILE:
|
---|
95 | POINTERS UPWARD FROM DEEPER SUBFILES:
|
---|
96 | POINTERS OUTWARD TO OTHER FILES:
|
---|
97 | POINTERS INWARD FROM OTHER FILES:
|
---|
98 | SQLI WORD-PROCESSING TABLE
|
---|
99 | - SUBSET OF SUBFILES
|
---|
100 | WORD-PROCESSING?
|
---|
101 | SQLI POINTING TABLE
|
---|
102 | - SELF-REFERENTIAL POINTERS
|
---|
103 | TIMES POINTED-TO BY ITSELF:
|
---|
104 | - UPWARD FROM THIS SUBFILE LEVEL
|
---|
105 | TIMES POINTING UPWARD (SUBFILE LEVELS):
|
---|
106 | SQLI POINTED-TO TABLE
|
---|
107 | - UP FROM ONE OR MORE SUBFILE LEVELS
|
---|
108 | TIMES POINTED-TO FROM BELOW:
|
---|
109 | (EXCLUDES SUBFILE POINTERS)
|
---|
110 | TIMES POINTING (GOING OUTWARD):
|
---|
111 | TIMES POINTED-TO (COMING INWARD):
|
---|
112 | WARNING: REPORT JUST WRITES TO THE SCREEN WITHOUT PAGE BREAKS
|
---|
113 | (INTENDED FOR SCREEN CAPTURES) SO PICK ONE TABLE
|
---|
114 | OR A SMALL RANGE WHEN TESTING
|
---|
115 | LABEL;TYPE
|
---|
116 | TBL:
|
---|
117 | COL:
|
---|
118 | SUBFILE OF:
|
---|
119 | This can take 5-10 minutes. Continue
|
---|
120 | Maximum pointing references
|
---|
121 | This cutoff is used as an upper limit on pointer links. Tables with
|
---|
122 | more links than this upper limit are displayed as the set of shared tables.
|
---|
123 | Others with common pointer links are then grouped together. The resulting
|
---|
124 | subsets could be used in SQL Grant statements.
|
---|
125 | Try using cutoffs between 3 and 10, comparing results.
|
---|
126 | Select a Table of Special Interest (Optional):
|
---|
127 | LISTING OF SHARED TABLES
|
---|
128 | SHARED TABLES =
|
---|
129 | (CUTOFF OF
|
---|
130 | DETAILED GROUP REPORT
|
---|
131 | DETAIL OF GROUPS =
|
---|
132 | GROUP:
|
---|
133 | COMPLETE REPORT OF ALL GROUPS
|
---|
134 | TABLE GROUPS =
|
---|
135 | TABLE COUNT=
|
---|
136 | PRINT OF JUST ONE GROUP (INCLUDING THE SPECIFIED TABLE)
|
---|
137 | The selected table doesn't fall in a group; see the shared set.
|
---|
138 | There isn't a group for the selected table; it doesn't have pointer links.
|
---|
139 | GROUP INCLUDING
|
---|
140 | ...... Please wait. Reports take a few minutes to process ......
|
---|
141 | FileMan SQL/ODBC interface tables
|
---|
142 | SCHEMA: RECORD INSERT FAILED
|
---|
143 | STATS: RECORD INSERT FAILED
|
---|
144 | STATS: KEY COUNT INSERT FAILED
|
---|
145 | EDIT-PROTECTING SQLI FILES...
|
---|
146 | EDIT-UNPROTECTING SQLI FILES...
|
---|
147 | Try again later. An SQLI projection is running right
|
---|
148 | now. It might take a few hours to finish, but then you
|
---|
149 | can try again and get a final status report.
|
---|
150 | SQLI DIAGNOSTICS REPORT
|
---|
151 | No date associated with first SQLI Table record.
|
---|
152 | No dates found in the SQLI Error Log.
|
---|
153 | Different dates on Table and Error Log files.
|
---|
154 | LAST SQLI TABLE UPDATE:
|
---|
155 | LAST SQLI ERROR UPDATE:
|
---|
156 | SQLI was run in the past. DDs may have changed since then.
|
---|
157 | No SQLI Schema records. Has the SQLI projection been run?
|
---|
158 | No records in the SQLI Table file.
|
---|
159 | All regular tables appear to have been built.
|
---|
160 | Not all files appear to have been built as tables.
|
---|
161 | The last regular file to be processed was
|
---|
162 | The next one, file
|
---|
163 | may be the problem.
|
---|
164 | The next one, subfile
|
---|
165 | No records in the SQLI Column file.
|
---|
166 | Columns have been built for the last table processed.
|
---|
167 | It looks like not all columns were processed.
|
---|
168 | The last file processed was
|
---|
169 | The last field processed was
|
---|
170 | The next field to be processed looks like
|
---|
171 | Having finished with all fields of
|
---|
172 | , SQLI was probably
|
---|
173 | trying to process
|
---|
174 | , the next file.
|
---|
175 | The last one (
|
---|
176 | ) is a subfile of
|
---|
177 | It is field
|
---|
178 | of file
|
---|
179 | That looks like the last field in
|
---|
180 | The next file to be processed looks like
|
---|
181 | The next subfile to be processed looks like
|
---|
182 | SUGGESTION: Investigate this file/subfile as the potential
|
---|
183 | source of the problem. That's:
|
---|
184 | No foreign key records have been built.
|
---|
185 | No table elements have been built for foreign keys.
|
---|
186 | All regular foreign keys have been built (FKs).
|
---|
187 | Parent foreign keys (PFKs) have also been built, the
|
---|
188 | last one being for file/subfile
|
---|
189 | Only regular foreign keys (FKs) have been processed.
|
---|
190 | The last was for file/subfile
|
---|
191 | No records for SQLI index tables.
|
---|
192 | Index tables don't appear to have been built.
|
---|
193 | Index processing stopped at file
|
---|
194 | All index tables appear to have been built. The last was for
|
---|
195 | No problems detected in SQLI data structures themselves.
|
---|
196 | Problems found in SQLI data structures.
|
---|
197 | See SQLI Site Manual, trouble-shooting section, for ideas about
|
---|
198 | how to investigate the problem. For example, RUNONE^DMSQ may be
|
---|
199 | used to explore a potential problem file.
|
---|
200 | DI,DIQUIET,DIFM
|
---|
201 | Time elapsed:
|
---|
202 | FIELD: CALL TO RETRIEVE ATTRIBUTES FAILED
|
---|
203 | DECIMAL DEFAULT
|
---|
204 | FM_MUMPS
|
---|
205 | SET_OF_CODES
|
---|
206 | FM_DATE_TIME
|
---|
207 | FM_MOMENT
|
---|
208 | FM_DATE
|
---|
209 | FM_FLAG
|
---|
210 | VARIABLE_POINTER
|
---|
211 | FM_MUMPS^245
|
---|
212 | Unable to proceed. Fileman version node ^DD(
|
---|
213 | ) is undefined.
|
---|
214 | Unable to proceed.
|
---|
215 | 0th node of ^DPT missing
|
---|
216 | Fileman version must be at least 17.2
|
---|
217 | Answer with PATIENT NAME, or SOCIAL SECURITY NUMBER, or last 4 digits
|
---|
218 | of SOCIAL SECURITY NUMBER, or first initial of
|
---|
219 | last name with last
|
---|
220 | 4 digits of SOCIAL SECURITY NUMBER
|
---|
221 | -Entry PATIENT List
|
---|
222 | Load/Edit Patient Data
|
---|
223 | Register a Patient
|
---|
224 | ...Patient not in database, use ADT options to load patient
|
---|
225 | Patient not found...Create stub entry:
|
---|
226 | Could not add patient to patient file
|
---|
227 | There is more than one patient whose last name is '
|
---|
228 | whose social security number ends with '
|
---|
229 | Are you sure you wish to continue (Y/N)
|
---|
230 | Warning : You have selected a test patient.
|
---|
231 | IORVOFF;IORVON
|
---|
232 | *** PATIENT ENROLLMENT END
|
---|
233 | *** PATIENT ENROLLMENT ENDING. ENROLLMENT END DATE IS NOT KNOWN. ***
|
---|
234 | Combat Vet Status:
|
---|
235 | BS5,CN,RM
|
---|
236 | CN,RM
|
---|
237 | BS,SSN,CN,RM
|
---|
238 | SSN,CN,RM
|
---|
239 | CN,RM,BS,SSN
|
---|
240 | CN,RM,SSN
|
---|
241 | ADDITIONAL MATCHES FOUND BUT NOT RETURNED
|
---|
242 | ENTER '^' TO STOP, OR
|
---|
243 | ADDITIONAL MATCHES FOUND BUT NOT
|
---|
244 | Unable to Add Patient. Your Fileman Access Code is undefined.
|
---|
245 | ...adding new patient
|
---|
246 | Please enter the following additional information:
|
---|
247 | A NEW PATIENT (THE
|
---|
248 | Enter 'YES' to add a new applicant, or 'NO' not to.
|
---|
249 | Sorry, '^' not allowed!
|
---|
250 | Entry in
|
---|
251 | ) refers to this patient
|
---|
252 | Unable to search for potential duplicates, Date of Birth and
|
---|
253 | Social Security Number must be defined.
|
---|
254 | ...searching for potential duplicates
|
---|
255 | No potential duplicates have been identified.
|
---|
256 | The following patients have been identified as potential duplicates:
|
---|
257 | Do you still want to add '
|
---|
258 | ' as a new patient
|
---|
259 | Enter 'YES' to add new patient, or 'NO' not to.
|
---|
260 | -1^required parameter not passed
|
---|
261 | -1^Could not add patient to patient file
|
---|
262 | and whose social security number ends with
|
---|
263 | Are you sure you wish to continue?
|
---|
264 | Patient name components--
|
---|
265 | Family name cannot be deleted!
|
---|
266 | (deletion indicated)
|
---|
267 | Invalid values to file, full name must be at least 3 characters!
|
---|
268 | Ok to file '
|
---|
269 | ' and its name components
|
---|
270 | Indicate if the edits to the name and its components should be filed.
|
---|
271 | WARNING: Do not enter single name values for patients (no given or
|
---|
272 | first name) unless this is actually their legal name!!!
|
---|
273 | Are you sure you want to enter the patient name in this manner
|
---|
274 | Specify 'YES' to enter a single name value, or 'NO' to discontinue.
|
---|
275 | Input values less than 3 characters in length must be all alpha characters.
|
---|
276 | middle name.
|
---|
277 | Middle names of 'NMI' and 'NMN' are prohibited.
|
---|
278 | name prefix, such as MR or MS.
|
---|
279 | suffix(es), such as JR, SR, II, or II.
|
---|
280 | academic degree, such as BS, BA, MD, or PHD.
|
---|
281 | Answer with this persons
|
---|
282 | The response must be
|
---|
283 | characters in length and may only contain
|
---|
284 | uppercase alpha characters, spaces, hyphens and apostrophes.
|
---|
285 | While editing name components, only jumping to other components is allowed!
|
---|
286 | Edited:
|
---|
287 | >>> Changing name of 'IRT TYPE OF RECORD' file (#393.3)
|
---|
288 | to 'IRT TYPE OF DEFICIENCY'...
|
---|
289 | .01///IRT TYPE OF DEFICIENCY
|
---|
290 | >>> Initialization of Version
|
---|
291 | of DPT Complete.
|
---|
292 | -1^No detailed description found
|
---|
293 | Data
|
---|
294 | -1^Getting submultiples not supported.
|
---|
295 | -1^Only a single field number allowed with the W flag
|
---|
296 | -1^The W flag must be used by itself
|
---|
297 | -1^No data retrieved
|
---|
298 | Field number
|
---|
299 | -1^Error Message
|
---|
300 | -1^Error text
|
---|
301 | FILE,
|
---|
302 | VALUE,
|
---|
303 | #################### #################### ####################
|
---|
304 | #################### #################### ####################
|
---|
305 | #################### #################### ####################
|
---|
306 | #################### #################### ####################
|
---|
307 | #################### #################### ####################
|
---|