How to connect remote server

  • Thread starter Thread starter MSK
  • Start date Start date
M

MSK

Hi,

I am a newbie to .NET/Networking

if I develop a project in

1. VB.NET + SQL server database
2. ASP.NET + SQL server database
3. .NET ( vb or asp) + Access database

Which one is advisable, in terms of hardware, security, cost...?

one more thing, my user has just internet connection (NTL- internet
provider)

If I develop desktop application (vb.net) and install in one
location , keep the server at another location, how can we connect?
can I achive via CODE ? any settings ? should internet provider
change anything for me ?

If I develop WEB app (asp.net), I can develop and install in the
server, how we can map these clients with the server via the private
network.

Will .NET (vb or asp) work with Access database (any performance or
functionality issues?)

Thanks
MSK.
 
Hi,

I am a newbie to .NET/Networking

if I develop a project in

1. VB.NET + SQL server database
2. ASP.NET + SQL server database
3. .NET ( vb or asp) + Access database

Which one is advisable, in terms of hardware, security, cost...?

one more thing, my user has just internet connection (NTL- internet
provider)

If I develop desktop application (vb.net) and install in one
location , keep the server at another location, how can we connect?
can I achive via CODE ? any settings ? should internet provider
change anything for me ?

If I develop WEB app (asp.net), I can develop and install in the
server, how we can map these clients with the server via the private
network.

Will .NET (vb or asp) work with Access database (any performance or
functionality issues?)

Thanks
MSK.
Click to expand...

Using Access is going to be the least secure, least robust, have the
lowest performance, handle the lowest number of concurrent
users...however if you can't afford SQL Server, it is an option and it
will work.

As far as which has better database support, web or desktop
application, well that all depends on your situation. Assuming this
is all on a local network, going for a desktop application means that
the database queries and result sets are transmitted to each end user,
and their machine will process the data. If they have decent
machines, this should be no problem. You won't be able to take
advantage of Multi-User Caching features however (which can greatly
reduce the number of database calls depending on the application) that
you would be able to with a web application. However you can get many
other advantages of it being a desktop application.

You also seemed to imply that you may develop a desktop app but store
the database offsite on a different network. Doing so may give you a
very slow application (depending on your queries and network) and
unless you connect via VPN or some other secure connection, your data
may be transmitted over clear text and easily obtained by any hacker.

As far as how to connect to the database, you can do so in code
through a connection string where you specify the server address,
database name, and login credentials. To connect to a web server,
just set your web app up in IIS on the web server, and point your
browsers url to that server. Here's a good tutorial site for how to
do this: http://samples.gotdotnet.com/quickstart/howto/doc/adoplus/ADOPlusOverview.aspx

Good Luck!
 
Back
Top