Remote ODBC connection into dasp SQL Server

[scmorley]

Hi,

I have recently opened a DASP.net account with a view to converting a local Access application, with a front-end/back-end split, onto a remote application. However, I'm not much of a techie, so am looking for some help.

What I was hoping to do at first was migrate the back-end onto my new dasp SQL Server and then have the local front-end Access app connect to it using ODBC linked tables. As the new UI is developed, functions can slowly moved off the local Access app onto the web-based version, all the while using the same data.

I was also hoping to keep a local .net application longer term for various reporting and administrative functions, although I will use a proper ADO connection for that.

My question is firstly, is this approach possible? And secondly, does it require any special configuration, such as allowing remote connections? My first attempts using ODBC caused a "SQL Server does not exist or access denied" error. However, the support desk suggested it was possible, but said I should ask you kind folks as they wont support this kind of thing.

Any comments and suggestions greatly appreciated.

Many thanks in advance,

Simon

[bruce]

it is possible.. providing your network allows the required port 1433 traffic to go through.

[scmorley]

Thanks Bruce. I had another go last night and got it to work.

In case anyone else is struggling with this, I found that when using the normal ODBC creation process in XP or Vista (tried it on both) I had to untick the option to "Connect to SQL Server to obtain settings for the additional configuration options". After this the process worked exactly as expected and the test connection at the end was successful. I then managed to link my tables as planned.

[mjp]

Interesting. Thanks for the follow up.