[2005] SQL Data binding and External Connections
Hi everyone,
I am in the process of writing a rather simple contact manager using SQL server 2005 and Databinding, however I have run into one small problem. This program will need to (occasionally) be run outside the local network.
Now its easy enough to open my servers SQL port (Of course after changing it to something else) and use SQL Authentication to connect externally to the database; but I am still concerned about security.
On the other hand, it’s also easy to create a service that manages all incoming connections to the server as a middleman between the app and the server; but then I lose my ability to databind the objects in my app.
Which is something that I very much want to utilize.
Could someone please comment on whether or not it really is such a no, no to open your SQL server to the outside world as some people claim, and if it is how could I use a "middleman" service but continue to use databinding?
Re: [2005] SQL Data binding and External Connections
Quote:
Originally Posted by maximg
Could someone please comment on whether or not it really is such a no, no to open your SQL server to the outside world as some people claim
That has nothing to do with VB.NET. This site has a Database Development forum for database questions.
Quote:
Originally Posted by maximg
if it is how could I use a "middleman" service but continue to use databinding?
The two are completely unrelated. You can bind any list of data you want to your controls. You can bind a DataTable or a collection of business objects. It would be "better" to use a collection of business objects regardless.
You should create your app with multiple layers. You can then have two separate Data Access Layers. One will be a Web Service that you can access from anywhere. The other will be a DLL that accesses a server on the local network. They would both expose the same interface so the next layer up in the app doesn't care which it's talking to.
