Greetings,
I've got myself into a little knot...
Here are the rough steps that have been done to date:
We wanted to merge a workspace into another workspace. IOW, bring all programs and data definitions
(from workspace SI) into an existing workspace (workspace IM).
We set the workspace sources in IM to look at the original workspace (SI) and created an import.
Everything was imported.
Created a group check out to move the PCODE to the correct modules (from module si-bat to im-bat) so
that all the source code will be in the same module.
Created a new module im-dbsi and did a "Load Schema" from the physical database. This is where
things have gone wrong.
The table names were created in im-dbsi and new table.fields that had been created in the database
due to some tables having the same name as in other databases already in the workspace.
The situation is this:
Table names in im-dbsi (new module created) with some fields.
Field names in si-dbm (old module) that was imported into new workspace without table names.
When expanding the table in im-dbsi, all the fields are displayed with Pmodule of si-dbm.
How can I move all the fields to be in im-dbsi? Or maybe move the tablenames back to si-dbm? Does
anyone understand what I've done?
I tried assigning or creating the fields again, but I get an error stating that that name exists
already. Anything else I should try?
Any help in untying this knot would be appreciated...
Regards,
Stefan
-------------------------------------------
Stefan Le Jeune
MIP Holdings
Cape Town, South Africa
+27.21.403-9555(Work)/+27.83.462-1766(Cell)
stefan@mip.co.za
I've got myself into a little knot...
Here are the rough steps that have been done to date:
We wanted to merge a workspace into another workspace. IOW, bring all programs and data definitions
(from workspace SI) into an existing workspace (workspace IM).
We set the workspace sources in IM to look at the original workspace (SI) and created an import.
Everything was imported.
Created a group check out to move the PCODE to the correct modules (from module si-bat to im-bat) so
that all the source code will be in the same module.
Created a new module im-dbsi and did a "Load Schema" from the physical database. This is where
things have gone wrong.
The table names were created in im-dbsi and new table.fields that had been created in the database
due to some tables having the same name as in other databases already in the workspace.
The situation is this:
Table names in im-dbsi (new module created) with some fields.
Field names in si-dbm (old module) that was imported into new workspace without table names.
When expanding the table in im-dbsi, all the fields are displayed with Pmodule of si-dbm.
How can I move all the fields to be in im-dbsi? Or maybe move the tablenames back to si-dbm? Does
anyone understand what I've done?
I tried assigning or creating the fields again, but I get an error stating that that name exists
already. Anything else I should try?
Any help in untying this knot would be appreciated...
Regards,
Stefan
-------------------------------------------
Stefan Le Jeune
MIP Holdings
Cape Town, South Africa
+27.21.403-9555(Work)/+27.83.462-1766(Cell)
stefan@mip.co.za