[ralph.wigham]

Hi,

I am developing an asp.net application and don't know what datasource to use. I have SQL Server on my machine to I can use access etc. but the server I want to deploy to only accepts .mdb files.

All the books I have on ASP.NET don't mention how to link a .mdb access database to a sql server. Specifically I am confused about stored procedures as .mdb doesn't support stored procedures (I think).

Any advice?

Cheers
R

[Joepas]

You could create an access data project which will act as sort of a frontend to an sql server, it can be a remote server, it doesn't need to reside on the same server as the .adp file..... I don't know how well (or if it will even) work as a data source for .asp pages though....

If the server that is hosting your .asp pages will only accept .mdb files, it sounds like they don't have sql server running, in which case you need to use tyour access database that you upload to the server as the datasource for your pages.

[ralph.wigham]

Cheers Joepas,

I eventually overcame the problem. I in the end used SQL server but was forced to re-write all my SQL into my actual application logic in asp.net. As it turned out writing direct into the applcation logic was much better than using stored procedures.

Unfortunately my server company whom I am contractually bound with until god knows when do run SQL server and accept asp.net, but only accept .mdb rather than .adp, which is odd. I have overcome this problem and performance wise, it is running much smoother with a .mdb and application level SQL. I just had to remember to establish a configuration level SQL connection to my datasource so I didn't have to re-write it to every web page I created.

Cheers for your reply. Are you too an asp.net developer?

R