Pros and cons of ADP compared to .Net

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello -

I have a rather small Access application which needs to have part of it on
the web. It needs to use Sql Server instead of Access for the backend.

I was wondering about the possibility of trying an Access Data Project.
I've never done one. Are they funky? When I think Web, I tend to think in
terms of .Net stuff.

Any thoughts are greatly appreciated!
 
Bad idea: with either a MDB file with linked tables to SQL-Server, ADP or
..NET, the probability if hight that these solutions will be blocked by a
firewall for many of your users if you are going over the web.

This might be the case even if you know each of your potentiel web users.
For example, most of today companies and organisations won't accept to open
the port 1433 for one of their employes so that he can access your
application. I had myself in the past an application that has been
completely dumped (and rewritten with something else) because of this.

Two solutions for you would be to use a .NET solution but this time using
web services to transmit data over the web (a more complicated solution than
simply using a direct link to the server) or to go with ASP.NET.

As of today, the future of ADP seems to be very dim because it looks like
that they are not really supported by MS anymore.
 
Hello Sylvan:

Thanks you so much for your response. I do not have experience with web
services and the lame examples (eg changing Fahrenheit to Celsius) from
textbooks have certainly not shed any light on the subject for me, nor have
they piqued my curiosity. Do you have a suggestion for a good book on the
subject?

I have access to a server that I can use for our local office. I do not
have access to the nationwide servers that are utilized for our intranet.
Our local offices network people have never set up the server for .net
deployment.

With our local server, though, can't I install IIS (and Sql Server) and
provide a .Net intranet solution for our local offices?

The only way I have deployed .Net sites in the past is to use Brinkster.

Any clues regarding the above will be appreciated!

Sandy

P.S. Why would a web service work
 
Intranet (LAN) and going over the Web (WAN) are two different things: you
can do many things over the LAN that you can't over the WAN.

In your case, the most simple solution would be to use a simple Access
application with linked tables to SQL-Server (if you really want to use
SQL-Server instead of JET as the Backend database). This will be a much
more simpler solution than ADP.

You can still take a look at ADP, if you want to, but it have many bugs.
There is a newsgroup specifically about ADP: m.p.access.adp.sqlserver.

With your local server, probably that you can install anything you want but
I cannot tell you anymore on this because I'm not your IT administrator.
 
Thanks, Sylvain!
--
Sandy


Sylvain Lafontaine said:
Intranet (LAN) and going over the Web (WAN) are two different things: you
can do many things over the LAN that you can't over the WAN.

In your case, the most simple solution would be to use a simple Access
application with linked tables to SQL-Server (if you really want to use
SQL-Server instead of JET as the Backend database). This will be a much
more simpler solution than ADP.

You can still take a look at ADP, if you want to, but it have many bugs.
There is a newsgroup specifically about ADP: m.p.access.adp.sqlserver.

With your local server, probably that you can install anything you want but
I cannot tell you anymore on this because I'm not your IT administrator.
Click to expand...
 
Back
Top