Kbase P35724: When assigning a menu/toolbar band to a object, RTB does not
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/08/2003 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.0A01
FACT(s) (Environment):
RoundTable 9.1x
FACT(s) (Environment):
Progress 9.1D
SYMPTOM(s):
When assigning a menu/toolbar band to a object, RTB does not checkout that object.
Which datasets should be imported in new workspaces.
CHANGE:
Example:
In a develop workspace (DEV) I introduce a new object type (as a specialized object type of an existing object type; subclassing).
Also introduce a new attribute and add it to my new object-type.
Also create a object of that new object-type and it also uses the new attribute.
When moving this to another workspace, it may be imported in the order:
- new object
- new object-type (ado file with all my customized object types)
- new attribute (ado file with all my own created attributes)
Does this import works?
During the import of the object (which contain a reference to the new object type + new attribute) these new object-type and attribute are still not in the target dynamic repository.
Or does this not effect the import?
CAUSE:
Bug# 20030806-009
FIX:
We expect that your import is going to be OK, even if the object types are imported last - as the dataset import does a copy of the data without any validation - except for the triggers. It may depend on which datasets are being imported.
In any case, you will not be able to use or run the new object in the workspace or target ICFDB into which you are importing, until the object type data has been imported as well. That is because the object type is validated by the framework when you try to access the object.