I just installed the trial edition, and the installation went fine (XP and Vista on the same PC).



However, they both have the same problem... I am unable to execute the Sample applications from the Sample Console because there is a problem connecting to the database. Note: This is in spite of installing the StrataFrame and StrataFrameSample databases (.mdf files) in SQLExpress... which is running as a service.



Any help would be appreciated.



Regards, Mike Niemann

My problem happens on the next step.   I connect to my SQLEXPRESS server fine.  But when I configure CustomersBO and try to select a table using the SQL Server selection, I get a Business Object Mapper Error ID 3 - An error occurred while attempting to open the data source with the connection string ....etc.   Exception - Cannot open database xx requested by the login.  Login Failed for user 'yyyy'.     When I change selection to DDT, I can access the sample tables just fine.   I can also access them thru the SQLEXPRESS management console.   Not sure why it is refusing my login when selecting SQL server.

When you view the properties on a project node in the BOMapper, there is a list of connection strings at the bottom.  Those are the connection strings that are used unless the connection string is overriden on the configuration for the individual BO (in the properties of the BO in the BOMapper).  Check those connection strings; it sounds like the "SQL Server Connection String" in the project properties is off.

It appears to be correct.  It is the same I use when I test connected using Visual Studio and it allows me access to the Strataframe sample database.   I'm using windows 8.1 and SQLEXPRESS 2014 if that makes a difference.   I tried both local\sqlexpress and  mycomputername\sqlexpress.   On the top level (BOMapper on Project level) it acts like both connect fine.   Then when I move to CustomersBO to configure it, as soon as I try to select a source it gives me the error if I"ve selected SQL server.

Hi Darrell,

Since you are using Windows 8.1, try opening VS as "Administrator", then test to see if that fixes the issue.

Edhy Rijo