There are several places that a connection string can be specified...all accessible through the designers. You can set the connection string in the data store (like you are aware). Second place is to open the BO Mapper properties (configure). There are connection strings that can be specified on a per project basis (DTEProjects). The third place is on the BO itself, which would just entail right clicking the BO and going into properties.

Yea, the 1.6.7 did the trick for SQL 2008.  One other issue though.  Once the Business Object Mapper (BOM) is open, it seems to be using a connection string stored in a table DTEProjects.proj_connectionstring instead of the connection selected in the "Application Database Connections" dialog.  This was causing the BOM to point back to the other server when configuring a new BO.  Is there a better way of changing this besides editing the table.

Good point...are you running 1.6.7 beta? If not then you will have to go there in order for this to work...in fact, I know that is what is happening at this point. SQL Server 2008 is only supported in the 1.6.7 build.

Hi Chris,



I forget the details now but when we moved to SQL 2008 it wasn't supported out-of-the-box by SF and we had to change references to SQL 10 in the SF sources. Maybe this is the problem - are you running the latest version of SF?



Cheers, Peter

Try SQL authentication...it is always hard to tell if Windows Auth is setup properly. Try logging in with SQL auth to see if you have better results.

This is exactly where it's not authenticating.  Attached message occurs when I click next.

When you go into the Database Connections and select the SF Data Store, click the Edit button and go through the wizard.  Does it authenticate?  This is the connection that is used.  So you if you can authenticate here, then all other SF pieces should be able to authenticate.

I guess I wasn't clear.   I can access the sql 2008 database from any computer via sql server management studio or our application using a connection string just fine (integrated or sql security).  When I try to setup a new database connection from either dev machine is when we get that message.    There has to be something different going on somewhere.  No doubt something I screwed up.   Is there anyway to tell what connection string is being used from the connection wizard?

Connecting is pretty straight forward. It uses a standard DbConnection (SqlConnection) using a standard connection string. So if you are having connectivity issues, double-check your connection string. Next, make sure that you can access the database from a machine OTHER than the machine on which it resides through SQL Server Management Studio or something along those lines. If you can connect in that regard, then the BO Mapper, DDT, etc. all connect the same way.

Double checked, this is how we have it set.  When we moved the application database over, we didn't have any problems (app runs fine pointing to 2008 using a connection string).  It's just when I tried to use the Database Connection Wizard and the Business Object Mapper.