Kbase P14820: Several objects have changed their code sub-types within Rou
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/29/2003 |
|
Status: Unverified
FACT(s) (Environment):
Roundtable 9.x
FACT(s) (Environment):
Dynamics 2.0A
SYMPTOM(s):
Several objects have changed their code sub-types within Roundtable
CAUSE:
BUG# 20021128-015
CAUSE:
It is not possible to change an objects sub-type within Roundtable if it is assigned to a workspace. This presents some problems when using Dynamics as we may change static objects to dynamic objects.
Current
Gscddcfdataset.w
Gscemimptw.w
Gscddcftablecomp.w
Gscobful2o.w
Iimport
scddcfdataset.ado
Gscemimptw.ado
Gscddcftablecomp.ado
Gscobful2o.ado
Rydynsdfmw.w
The above current objects MUST be deleted from all workspaces before performing the partner-site load or importing the new objects from 090dyn-dep otherwise the import process will fail with an error.
If you have not deleted these objects before doing the import · an error saying that Roundtable is unable to create the file due to the fact that another object within the workspace uses the same physical file is displayed. At this point, the DCU then attempts to run · this is not desirable.
DO NOT RUN THE DCU until all objects have been imported into your workspace successfully.
If using the Roundtable incremental update · these objects fail to load during the partner site load because they have changed code sub-types.
It is not possible to delete the object Gscobful2o.w from a Workspace if the ICFDB database is connected. Even if you say no to deleting this object from within the Dynamics repository (which is necessary due to it being referenced in several other objects) the Dynamics delete trigger still fires.
FIX:
Workaround
Delete these objects in the 090dyn-dep BEFORE doing the incremental upgrade.
This is not a problem in the 090dyn-dep Workspace if doing a full partner-site load (as the 090dyn-dep workspace does not exist until you perform the partner-site load)
This will always be the case if an object changes its sub-type within Dynamics. There has to be someway of identifying these objects BEFORE the import process so that these objects can be deleted from the target workspace. This will become more and more important as objects are changed from static to Dynamic within the Dynamics framework itself.