This was puzzling to us as well.  We ran a class last year on asp.net development, and were confused by sql server telling us it did not have a trusted connection.  This article sheds some light on the problem:  http://support.microsoft.com/default.aspx?scid=kb;en-us;815154&Product=aspne

But I am wondering how to set up a lab of machines using VS so that they can access SQL server without having to add each individual machinename\aspnet account to SQL Server security.  Is there a way to tell VS in some config file to use a different default method for authenticating against sql server

Thanks

Joh
   
    ----- Dave Strickland wrote: ----
   
    When you drag and drop the connection onto your form you should be able t
    edit the connection string. If you want to force a connection to appear a
    SQL authentication in Server Explorer. Add a new data connection in th
    server Explorer("Right Click 'Data Connections' and Select 'Add new'"
    specify the server the userID and the Password you want to use
   
   
    "newbie" <bari@sos.REMOVETHIS.state.ga.us> wrote in messag
    news:OIsUGRJLEHA.1416@TK2MSFTNGP09.phx.gbl..
    > I'm running SQL Server 2000.  When I originally set up the localhost,
    se
    > it for Windows Authentication.  For the purpose of going through a
    ASP.NE
    > project in a book, I changed the properties to SQL Authentication (usin
    > Enterprise Manager).  However, when I visually connect to the database, i
    > VS.NET, it still creates a connection string using Windows Authentication
    > and furthermore does not allow that property to be edited.  What would b
    > causing this.  Thanks in advance
    >> Bar