How to code DATA SOUCE

?ve spent the last few months going crazy trying to write a connection string to allow me to insert information into my database. The database called ?capsDb1.mdb is located in my app_data file. The following code which points to a copy of the database on my ?C:? drive works well
Data Source= " &amp; C:/capsDb1.mdb")</o>
However, when I point to a copy of the database in my app_data file locate in the visual studio 2005 project file I get an error message.</o>
Data Source= " &amp; ("~/App_Data/capsDb1.mdb")</o>
Error msg: </o>
'C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\~\App_Data\capsDb1.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides</o>
As far as I can tell this is a valid path. Can any one help me or tell me where I can go to get help?</o>
Charlie

 

Connecting to an access DB with ASP.NET or classic asp you do best to use a path method.
Shown below is a successful ASP.NET connect I used here to an access DB.
If you need specific help let me know, no problem at all.
Salute,
Mark

 

Thank you for your help, but I still can?t get the code to work. When I try the following code:
</o>
Dim strConn As String = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source= " + Server.MapPath("../App_Data/capsDb1.mdb")</o>
</o>
Or this code:
Dim strConn As String = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source= " + Server.MapPath("../_database/capsDb1.mdb")</o>
</o>
</o>
I get an error message:
</o>
Server Error in '/bin' Application. </o>



'E:\web\findcausene\htdocs\bin\.._database\capsDb1.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. </o>
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.OleDb.OleDbException: 'E:\web\findcausene\htdocs\bin\.._database\capsDb1.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

Source Error: </o>




</o>
Line 14: </o>
Line 15: conCID = New OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source= " + Server.MapPath(".._database/capsDb1.mdb"))</o>
Line 16: conCID.Open()</o>
Line 17: '</o>
Line 18: ' cmdSelectCID = New OleDbCommand("Select[CID] FROM [Characteristics Table] Order by [CID] Desc", conCID)</o>

Source File: E:\web\findcausene\htdocs\bin\Test1.aspx.vb Line: 16

Stack Trace: </o>




</o>
[OleDbException (0x80004005): 'E:\web\findcausene\htdocs\bin\.._database\capsDb1.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.]</o>
System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection) +1131233</o>
System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) +53</o>
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27</o>
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47</o>
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105</o>
System.Data.OleDb.OleDbConnection.Open() +37</o>
Test1.Page_Load(Object sender, EventArgs e) in E:\web\findcausene\htdocs\bin\Test1.aspx.vb:16</o>
System.Web.UI.Control.OnLoad(EventArgs e) +99</o>
System.Web.UI.Control.LoadRecursive() +47</o>
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436</o>
</o>



</o>
I?ve spent over a day trying to debug this problem. What is the next step.?</o>
</o>
Charlie</o>

 

Oops, my bad...Not sure why I put those path climbers there, must have been groggy.
Good catch!