Hi Tim,
no I didn't see that error at all, though I didn't try running it until after changing the strings. I'm running vs2008 and looks like same version of mm (6/13/2008). A minute ago I changed to the connection string from vs|Server Explorer|Data Connections, different syntax but worked fine:

(I took out the userid & password) Data Source=PLUTO;Initial Catalog=Northwind;Persist Security Info=True;User ID=xxx;Password=xxx"

I'm on a test environment not on a domain.

-Larry

>Hi Larry,
>
>Did you get the same error Patrick was getting until you changed your connection string?
>Tim
>
>>>I recently installed the new 6/13/2008 release of MM.NET. I changed the App.config files in both the Business object project and the windows forms project and copied the connection string straight from the properties of the Server Explorer | Data Connection in Visual Studio 2008.
>>>Whenever I try to run the sample app, I get a SQL client error. From the stack (below) it looks to me that there is a problem somewhere in that I am using a named instance of SQL Server. Please note that "Server" line near the top of the call stack shows two backslashes:
>>>
>>> Server="DIS-PMCDERMOTT2\\PMCDDEV"
>>>
>>>Here's my connection string from the App.config:
>>>"Data Source=DIS-PMCDERMOTT2\PMCDDEV;Initial Catalog=Northwind;Integrated Security=True" (Only one backslash)
>>>
>>>My suspicion is this is an issue with a missing escape character for C# somewhere that is not liking the backslash in a named instance SQL name.
>>>
>>>Anyone have any ideas how to fix this? I'm at a loss. TIA.
>>>Patrick
>>
>>Hi Patrick,
>>I'm no expert, they're probably off today <g>, so in the mean time perhaps this will help:
>>my connection string entry in both app.config files for integrated security is
>>value="server=Pluto;Integrated Security=True;database=Northwind;"
>>
>>Pluto being my server running one instance of MS SQL. I also had to ensure the desired user had permissions of course.
>>
>>-Larry