Re: Split DB over the internet with SQL backend?

The ADO technology used by the ASP application and the ADO technology
used by an Access ADP or an HTA are identical. It is ADO that connects
to and communicates with the SQL-Server.
It is true that the ASP/ADO connection is not following the same route
across the internet as an ADP would; on the other hand, as I pointed
out, to accommodate different needs I have created almost identical ASP
and HTA applications. The HTA applications run solely on the
workstation and there is no noticeable difference in their performance.
(A subjective opinion is that they are faster.) As I have pointed out,
they have been used across Europe without any troubles with speed. I
have sat at night and discussed transactions we were both looking at
(in the HTA) with colleagues on Yahoo Server. When she updated a record
and saved the changes were immediately visible to me upon a refresh.
Speed was never a problem. It would be quite tedious to provide an ADP
or HTA example as one would have to do considerable work to protect
logons and passwords; I felt the columns ASP was an example that showed
the potential for MS-SQL over internet.
BTW, the Columns ASP is simply a port of a reference page from an
application that accommodates, among many other things, execution of
dynamically created SQL strings and/or the display of recordsets from
same. I mention this to point out that MS-SQL over the net is entirely
manageable.
Of course, I do not know the internet connection speed of the OP and
his clients. If he is using or testing a 56k dial up, then he'll be
aware that everything is dead slow. But I doubt that he is. I have
created, sold and delivered ADP applications that connected to MS-SQL
over the internet. Both were programmed to use an internet connection
to the Server when the local connection was not available. Managers
used these applications when they travelled, perhaps with different
speeds and qualities of connections. Again, there were no problems.
Clearly, you and I live in different worlds. One does not wait for an
hour for an ISP response to a problem here.
You have mentioned the design of the application as a factor in speed
and reliability. Some of the examples I have given are ADPs with bound
forms no different from MDBs using local tables. ADP connections are
surely not efficient as there are often multiple connections from one
ADP.
I believe the OP wanted to know if Access-MS-SQL over the net
applications are feasible and from experience, at least five years of
experience, I can say, "Yes!"

.

Relevant Pages

  • Re: Split DB over the internet with SQL backend?
    ... used by an Access ADP or an HTA are identical. ... It is true that the ASP/ADO connection is not following the same route ... speeds and qualities of connections. ...
    (comp.databases.ms-access)
  • Re: 2003 ADP corrupting when cannot connect
    ... the ADP seems more stable and less likely ... BaseConnectionString property BEFORE attempting a new connection. ... > | I agree with you that most likely the clients are less patient and try ... > | | corrupt. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: APD connect manually only
    ... I just want my ADP not to connect on startup. ... start a connection on startup as this takes too much time. ... has no effect on the information used to connect; it persists. ...
    (comp.databases.ms-access)
  • Re: Access 2003 to SQL Server 2000 over a VPN
    ... I would recommend looking at the possibility of using an ADP, rather than an MDB, but there's the distinct disadvantage that ADP may not be well-supported in the future. ... I'm using a fairly complex database using and ADP as the front end over a VPN connection. ... I have a client who has a simple Access database, which he now requires to be accessible to up to 50 concurrent users remotely over the internet, as well as a small number of local LAN users. ...
    (microsoft.public.access.adp.sqlserver)
  • RE: Access Front End & SQL Server Back End Connection
    ... I believe that if you're using SQL Server, unless you have a need for the ... additional capabilities afforded by use of a .mdb (e.g., ... tabling, heterogenous data source linking, etc.), then stick with an .adp. ... > grips with the options and settle on a good approach to making the connection ...
    (microsoft.public.access.modulesdaovba)