Cool I figured it would!

Thanks again. Upgrading to 1.6.7 solved it.

It will be done through the installation. There is nothing that you need to do other than load the SF update and allow it to update the structures.

Thanks Trent, I'm upgrading to 1.6.7 right now.



Is there an easy way to migrate the 1.6.6 strataframe database to the 1.6.7 version?

Then this could very well be there. At a minimum I would load the 1.6.7, even though it is stated as being a beta, it really isn't. The only reason it never made it into an official state is because of the documentation and samples.



That being said, we are also very close to a 1.7 official release. But you will need to come up to a more recent version before we can really dig into it anyway.

It's version 1.6.6

I have never seen this before....there have been a number of changes over the last 12 months. What version are you running?

Also, the 2 class lib projects are in the same solution.

I just want to say that I just create 2 class lib projects very quickly each with one BO and the same thing happened.

I have this situation too.



I have 2 BO class libraries.



The first one was coded using the namespace "WebI2" and has the InvoiceDetailBO class (for example). I used the BO mapper with this VS project and made some customizations. The BO mapper project name is "WebI2 Business Objects". everything here is working fine.



Then I create a second class library with the namespace "VFPWebI2". This one also has an InvoiceDetailBO class... same class name. I opened the BO mapper and created a new project (in BO mapper) that uses a different database... "VFP WebI2 Business Objects" for this new class library.



When I build the partial for InvoiceDetailBO on the second project the InvoiceDetailBO.Designer.cs file uses the first project's namespace "WebI2". It should be using "VFPWebI2".



Please help.



Thank You,

Govinda