Consultor Eletrônico



Kbase P25706: Under CorVu Graphical Analysis - column descriptions appeari
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   10/30/2003
Status: Unverified

FACT(s) (Environment):

Windows 2000

FACT(s) (Environment):

CorVu 4.20

FACT(s) (Environment):

Progress 9.1D

SYMPTOM(s):

Under CorVu Graphical Analysis - column descriptions appearing instead of column names.

Under Graphical Analysis - table descriptions appearing instead of table names.

CHANGE:

Reinstallation of CorVu.

CAUSE:

A column description can be changed at any time using the CorVu Knowledge Library. The entry in the Description field defaults to the column name (or column description in the underlying system catalog, depending on the platform), and is used to identify the column to the user throughout the system.

Modifications to the column description are saved in the .dct file associated with the database. The name of the file is 8 characters long. If, for example, the database is called sports, the associated .dct is sports00.dct. The .dct files are located in the CorVu\Dict directory or in the subdirectory specified when the CorVu server was created.

The reason for the behaviour is that CorVu is using a different .dct file than the one the user is expecting - the file has been moved, deleted, or the wrong subdirectory was specified when the server was created.

The .dct files can't be manually editted. They are updated via the Knowledge Library.

If this was working before - i.e. that you saw a short name rather than a full description - that means that there must previously have been a dct file for that database. The required dct file should be in the Knowledge Library directory associated with each database/database connection that gets configured.

In general you should keep the knowledge library directories under the default dictionary directory because this makes it easier to administer backups. The initial value in the knowledge library directory box is the default dictionary directory, so you can put your new knowledge library in that directory by adding a "\" followed by a subdirectroy name.

When setting up the server under the CorVu Administer there is a fill-in in the interface called Knowledge Library Directory. Perhaps the fill-in is referencing a different subdirectory than it previously was.

For example, suppose you create a server called "91dserver". This server connects to a database called sports91d. The corresponding dct file is "sports91", and you could locate it in F:\CorVu\dict\91dserver. This is the directory specified when creating the server.

FIX:

1. Check for other .dct files that might be associated with the database and use them. If it is the case that you do have what appears to be an earlier dct file for the database but it is located somewhere else, then you could either -

1.1 Backup the one that you are currently using, then copy the earlier one into the directory specified in the server configuration.

Or -

1.2 Reconfigure the server to use the directory where the earlier dct is stored.


2. If there isn't an earlier dct available, then the descriptions can only be altered from the Knowledge Library, by modifying the column description.

The following is extracted from the CorVu Knowledge Library online Help:

Changing a column description

A column description can be changed at any time using the CorVu Knowledge Library.
The entry in the Description field defaults to the column name (or column description in the underlying system catalog, depending on the platform), and is used to identify the column to the user throughout the system.
Remember that the entry in the Description field is the column name seen by the users throughout the CorVu system. A change in the Description field does not change the name of the column within the table.

To change a column description:

1. Select the column you wish to change.
2. Highlight the existing entry in the Description field.
3. Type in the new entry. The new description is automatically saved when another column, table, or database is selected. Remember that only one user at a time should be making changes to a shared Knowledge Library.