Database and SQL

STORE RECORD is the correct statement in Model 204 for adding new records to a file. The STORE command combined with RECORD specifies that a complete record should be stored.

The ADD statement is used to add new field values to an existing record in Model 204. This is different from STORE which creates new records.

In Model 204 file architecture, Table B contains the actual record data, including all retrievable field values for the records in the file.

DELETE is the M204 statement that removes fields from a record. DELETE RECORD would remove the entire record, not just fields. DELETE FIELD and REMOVE are not valid M204 syntax for field removal.

FPC (Find and Print Count) is the M204 command that counts and displays the number of records satisfying a condition. WOL is for ordered retrieval, FCOUNT is not a valid M204 command, and FRC is not a standard command.

The FOR EACH RECORD IN ORDER BY statement both retrieves and loops through only the FIRST occurrence of a field in each record, not all occurrences. This is important when you want to process unique records without duplicate field values. Option A correctly describes this behavior. Options B, C, and D are incorrect because the statement doesn't just loop without retrieval, doesn't process all occurrences, and isn't limited to the last occurrence.

The COUNT IN clause refers specifically to the count value generated by the COUNT OCCURRENCES statement, not to counting 'IN' keywords or database files. This allows you to use the occurrence count in subsequent operations. Option A correctly identifies this relationship. Options B and D are incorrect because COUNT IN doesn't count keywords or use a generic Count statement. Option C is incorrect because it doesn't count database files.

The VALUE IN statement can be used with ADD, CHANGE, and STORE RECORD statements in Model 204, making it versatile for field manipulation. It allows you to reference specific values within these operations. Option D correctly states that VALUE IN works with all three statement types. Options A, B, and C are incorrect because VALUE IN isn't limited to just one of these statements - it works with all of them.

The statement 'CHANGE FULLNAME TO' with no value specified is equivalent to 'DELETE FULLNAME' - it removes the field from the record. This is a shorthand way to delete a field without explicitly using the DELETE command. Option D correctly identifies this equivalence. Options A, B, and C are incorrect because they attempt to assign specific values (NULL as keyword, string, or number) when the actual operation is deletion.

The correct syntax in Model 204 User Language for placing records onto a list is PLACE RECORDS IN label ON [LIST] listname.

The ADD statement in Model 204 can only be used to add new field values to a record within the FOR EACH RECORD loop. This restriction ensures that additions are properly context-aware and associated with the correct record. Option A (True) correctly states this limitation. Option B (False) is incorrect because the ADD statement cannot be used outside the loop context.

In Model 204, the CHANGE statement modifies an existing field value, or adds the field and its value to the record if the field does not already exist in that record.

In Model 204 User Language, when you want to loop through and process records that are stored in a list, you must use the FOR WHICH statement to iterate over the list members.

LIST$ is the correct syntax to reference a list collection in a FIND condition. The $ symbol is the standard identifier for list variables in this system, while other options either use incorrect keywords or incomplete syntax.