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

Yes, to update a single database, you will need to run the Deploy to Server option within the DDT for the open profile.  To encapsulate the database deployment within an application, you will need to use the MicroFour StrataFrame DBEngine.dll assembly.  It contains the MicroFour.StrataFrame.DBEngine.DatabaseMigrator class.  This create a new instance of this class and use its DeployMetaData() and DeployData() methods to deploy the structure and the static data, respecively.  Each of these is non-blocking and raises events to show the progress of the operation.  Within you're application, it would be probably best for the app to store off the last modified date of the shared .pkg file within the registry.  If the data changes, then re-deploy the structure.