Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<h3>Initial Hints</h3> <p>If you want to see some examples for windows forms connecting to a database i can recommend the <a href="http://msdn.microsoft.com/en-us/vstudio//bb466226.aspx#formsoverdata" rel="nofollow noreferrer">forms over data video series</a>. Video 2 is about <a href="http://msdn.microsoft.com/en-us/vstudio/bb643826" rel="nofollow noreferrer">how to connect to a database</a>. </p> <p>In the app.config file you can put your connection data</p> <pre><code>&lt;connectionStrings&gt; &lt;add name="OrderManager.My.MySettings.OMSConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\OMS.mdf;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient" /&gt; &lt;/connectionStrings&gt; </code></pre> <p>To be able to help you better i need more details. If you connect in management studio you can take a look at your connections properties. What are the values here and so on.</p> <h3>Update</h3> <p>There is <a href="https://stackoverflow.com/questions/13215172/database-connection-error-file-in-use">another question</a> with a similar problem. May be you are <a href="http://blogs.msdn.com/b/sqlexpress/archive/2006/11/22/connecting-to-sql-express-user-instances-in-management-studio.aspx" rel="nofollow noreferrer">running user instances</a>. Please add more details:</p> <ul> <li>add information about your connection string (i am assuming your are using <a href="http://msdn.microsoft.com/en-us/library/ms233763%28v=vs.80%29.aspx" rel="nofollow noreferrer">file attached connnections</a> with a <a href="http://msdn.microsoft.com/en-us/library/ms246989%28v=vs.80%29.aspx" rel="nofollow noreferrer">local data file</a>)</li> <li>where do you click on your database? Are you clicking on the mdf file or are you using management studio or visual studio</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload