I have some work / testing done on PC1, I want to move it to PC2. How?

When I do a clean install of DDT to PC2 and select "Open Profile" all I can select is "New".

This leads to another question, sharing "profiles" or metadata and implementing databse/table updates.

Right now we use Stonefield, so I equate the DDT to that. If I make changes to table structures I know to make certain files available for other developers to import to their workspace, then the framework detects the changes and updates the databases in place.

So, how do I move/share/update DDT metadata (.pkg files correct?) to 1) another box 2) other devs 3) client sites.

Our current framework has the ability to update database structures in place when it detects that we have updated the meta-tables. Does SF do this?

I guess I have made a few assumptions about the DDT and want to clarify it feature set.

I am practically just trying to move my "play stuff" to my laptop for Friday and issues with that led to these other questions.

Thanks.

Keith Chisarik

Both PC1 and PC2 need to point to the same SQL Server database in order to both be able to see the profiles that have been created.  All of the meta-data is stored within the StrataFrame database and is only exported to the .pkg file to be deployed at a remote site.  So, to copy the data from two computers that cannot see the same database, you will need to a) copy the data from database A to database B or b) create a .pkg file for the profile on PC1 and create a new profile on PC2 and then import the .PKG file from PC1 into the new profile on PC2.

As for the framework detecting the changes to the meta-data for business objects, any time a structure change is made, you must open the Business Object Mapper and rebuild the partial classes for the tables that have changed.  This will update the structure on the business objects to match the current structure of the meta-data, sql tables, etc.