Kbase P25219: RoundTable. Creation of toolbar will fail
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/05/2003 |
|
Status: Unverified
FACT(s) (Environment):
RoundTable 9.x
FACT(s) (Environment):
Dynamics 2.0A
SYMPTOM(s):
RoundTable. Creation of toolbar will fail
CAUSE:
SCM Integration:
- If you try load load a toolbar using the XML export utility in RoundTable
(tools/dynamics/xml-export, make sure you have a task open), the load will
fail with an error message that the suffix must be .w instead of .ado.
- Same error will came up if you try to create a toolbar with the toolbar/menu designer.
FIX:
This issue is a result of the close links we have between object types in Dynamics and Code Subtypes in RTB. This link is being changed in the coming release to remove the need for a one-to-one link between Dynamics and RTB for
object types and code subtypes.
The issue here exists for historic reasons when the SmartToolbar object type was changed from being static to being dynamic. When this was done the support for this object type in SCM was broken, as the number of physical files
involved changed.
To get around the current problem, the following workaround can be used:
1. Create the toolbars in a Dynamics session without RTB connected
2. Dump the individual .ado files for the toolbars
3. Use Module Load in RTB to load the toolbar into RTB - but with a Code Subtype of "LsmartObject" instead of SmartToolbar. This is a generic single part Code Subtype.
When this is done, the data for the toolbar will be maintained as any other object (even though the Object type in Dynamics and in RTB are different) also for deployments, migration between workspaces etc.
When the changes to the Object Type - Code Subtype link have been implemented, this workaround will no longer be needed.