FCO-IM Casetool v4.1 - Frequently Asked Questions

This sections will only address issues in version 4.1 of the FCO-IM Casetool.

Problem (Short Description)

  • Multiple identical object or fact type expressions
  • No automatic matching of an object type expression

Problem (Full Description)

  • After classification and qualification of several fact-expressions a fact type has multiple identical object or fact type expressions.
  • The expression interface does not automaticly match an object type expression.

Possible Reason 1

You are classifying or qualifying expressions using a normal text file instead of an expression file.

Note that an expression file always starts with [EXPFILE, WIN] or [EXPFILE, DOS].

Limitations of normal text files:

  • You cannot select or classify/qualify multiple expressions.
  • The fact type name is not recognized by the FCO-IM Casetool and will not be automatically assigned to the fact-expression.
  • In version 4.0 quotes (") are interpreted as part of the expression. Version 4.1 has better quote handling.

Possible Reason 2

You have spelled an object type expression with or without a capital:


  • Equipment: A video is placed in room 1.2
  • Equipment: A blackboard is placed in Room 1.2
(Please note the captital letter of 'Room' in the second expression)

Classification / Qualification:

  • Equipment: < Facility> is placed in < Room>
  • Facility: A < facility name>
  • Room: room < room number>

The second expression is not automaticly matched with the first expression because of the capital mismatch. (We have choosen a rather strict approach).

For more information about expression files please refer to Lesson 4: Editing Information Grammars from your FCO-IM Casetool manual.


Problem (Short Description)

Generated output file does not execute.

Problem (Full Description)

When trying to execute a generated output script it does not execute.

Possible Reason

You might have been using reserved keywords as table, domain or columnnames.


Problem (Short Description)

Problems when opening an expression file.

Problem (Full Description)

After opening an expression file the fact type names between [] are not highlighted and it isn't possible to select more than one expression at the same time.

Possible Reason

The expression file should start with [EXPFILE, WIN] or [EXPFILE, DOS]. If you're still using version 4.0 of the FCO-IM Casetool these words should be written in capitals. In version 4.1 it's case-insensitive.


Problem (Short Description)

The generated output for MS Access 2.0 cannot be used in MS Access 7.0.

Problem (Full Description)

When executing a MS Access 2.0 Visual Basic for Applications script in MS Access 7.0, MS Access 7.0 does not execute the script.


Several constants in VBA (Visual Basic for Applications) for MS Access 2.0 have been renamed in MS Access 7.0. A separate MS Access 7.0 plug-in module is available in the Desktop Edition of the FCO-IM Casetool.



  • How do I change the identification of an object type?
  • What are the preconditions for the 'Replace Object Type'-function?


The example below illustrates how to change the identification of an object type.

Suppose you have an object type Project with the expression types and tuples as shown below:

  • F1: "There is a project < project nr>"
  • O1: 'project < project nr>'
  • O2: '< project nr>'


  • 100
  • 101
  • 102

You should now create a new object type with:

  • At least one fact type expression
  • An object type expression for each existing object type expression.
  • A tuple for each existing tuple.

To do this follow the steps below:

1. Rename Project into OldProject

2. Classify and Qualify the following expression:


"There is a project PA"

Where PA is a project name.

3. Classify and Qualify the following object expression:


'project PA'

Note: Select the 'Create OTE' option in the first screen of the classification/qualification dialog.

(Assume this object type expression is assigned number O14)

4. Classify and Qualify the following object expression:



Note: Select the 'Create OTE' option in the first screen of the classification/qualification dialog.

(Assume this object type expression is assigned number O15)

5. Extend the population of Project until it has 3 tuples by adding the project names: PB and PC.

You can extend the population by:

  • Selecting Project in the IG Viewer
  • Selecting the first expression
  • Choose 'Edit Population' from it's popupmenu.

6. Select OldProject from the IG Viewer and choose Replace from it's popup-menu.

7. Select Project as a replacement for OldProject.

This completes the replacement.

What will/should happen:

  • Everywhere O1 is used, it should be replaced by O14.
  • Everywhere O2 is used, it should be replaced by O15.
  • Where regenerating expressions (for example by examining them from the IG Viewer) the labels 100, 101 and 102 will be replaces by PA, PB, PC.

You could also replace the object type with more complex structures (multiple roles, nominalized structures etc.), as long as the new object type has a new object type expression for each existing object type expression and has a new tuple for each existing tuple.



The FCO-IM Casetool reports: 'File build version (21) is not compatible with current build version (20)'.


All Project files, IG files and IGD files created in the FCO-IM Casetool v4.0 can be opened without conversion in the FCO-IM Casetool v4.1. But when opening files in version 4.0 which where saved in version 4.1, the FCO-IM Casetool v4.0 will give an error message like this:

Error reading file: XXX

File build version (21) is not compatible with current build version (20)

In version 4.1 you can save files in the 4.0 version format by checking the necessary option in the Environment Options window.



When using an expression file for classification & qualification the FCO-IM Casetool reports: 'Index violation on index 'OTFT.name''.

Usually the FCO-IM Casetool will also pop up the message 'Do you want to end the automatic classification and qualification...'.


The names of object types / fact types may be up to 40 characters long.

When using an expression file for classification & qualification this maximum length is not checked properly by the FCO-IM Casetool. This causes the index violation when commiting the qualified expression.


If you encounter this problem please shut down the FCO-IM Casetool. Reopen the casetool and your last project. Open the expression file and manually reduce the length of your object types / fact types names to 40 characters maximum before starting the automatic classification and qualification.



Is it possible to define data types other then char or numeric?


Yes. As different databases have different names for their data types, we have choosen not to set the number of data types to a fixed list. When you edit a label type you can select one of the suggested data types from the combobox or you may enter any other custom data type name (e.g. SMALLINT).



When I copy my project to floppy it doesn't seem to work elsewhere. What happens?


Your project contains many separate files. You should copy all files included in your project to floppy. This means all IG's, IGD's, expression files and the project file itself. It is importent to maintain the same relative directory structure, so if you saved all your diagrams to a subirectory DIAGRAMS you should use put this subdirectory onto the floppy as well.



When I enter an existing object type / fact type name in the Edit OTFT-box by accident, canceling the box seems not possible.

Reason and Work-around

The validity of the new object type / fact type name is always checked even when cancel is pressed. Press the ESCAPE-key to cancel this box.