I updated my application project database using the DDT and verified the results in SQL 2005. I can also see the changes in the  BO Mapper. I did full and partial build and but cannot see my changes in the project BO themselves? I have cleaned/rebuilt and checked the configuration in the BO Mapper. It is pointing to my Project. I cannot figure this one out? 

Version 1.6.6

Vista

Michael

Are you talking about the partial classes or the StrataFrame database is not being updated when you choose a configuration within the BO Mapper?  This would make a very big difference in my diagnosis.

Yes!

Sorry, the database is updated by partial classes not working,

That sounds like an environment issue with Visual Studio.  That is much more difficult to diagnose.  I have never heard of this before which is generally a clue when there is an environmental issue within VS.  We actually talk directly to the VS DTE which in turn talks to the VS engine.  This is done so that we respect all security and logic within VS such as source control, permissions, etc.  Check these types of items:

• Source control
• Windows permissions as well as source control permissions if using source control
• Disk space

Things of the above nature would be where you want to look.

Strange because it works fine with my other projects on the same laptop?

VS2008

28gigs free.

Well, the disk space was just an idea of the types of things that could cause a problem.  If other SF projects are working, the the first thing I would do is create a blank solution and add existing projects in one at a time to see if things start kicking again.  I really don't know exactly what you are fighting, but it sounds like corruption or environmental issues.

Ok, I was wrong. I can see the new columns in the BO but cannot not see them in the BO attached to forms via the SF controls? I can see the updated items when I reference the BO items using intellesence though.

This is normal Visual Studio behavior.  Depending on how you are referencing the assemblies, etc.  Even while you are in the designer, the assemblies get loaded into the AppDomain.  Many times, the AppDomin will not release those older assemblies when new ones are build within the esigners.  So if you build the solution, get out of VS, and then come back in, they will be there.  If you use file referenfces rather than project references, then many times you can do a rebuild and they will show up.  But this is normal VS designer behavior.