Re: Created on Access 2003, but.......................



David W. Fenton wrote:
Bri <not@xxxxxxxx> wrote in RY1bg.173162$P01.155882@pd7tw3no:">news:RY1bg.173162$P01.155882@pd7tw3no:


David W. Fenton wrote:

Bri <not@xxxxxxxx> wrote in
G6Pag.172842$WI1.168410@pd7tw2no:">news:G6Pag.172842$WI1.168410@pd7tw2no:


David W. Fenton wrote:

. . . Believe what you want but both are true. What reason would I have to lie about it? What
proof do you require other than my word? I don't like the
implication that I am making things up. I can prove everything I
have stated in this thread.


If you can't show on the ISP's website that they support it, then
I don't believe it. It's just not something any sensible ISP
would do.

Well, I found a page that explains how to connect to the db from
your PC using MySQL Administrator. It connects from the outside
using the Server name and port.
http://kb.brinkster.com/Kb.asp?kb=111189


I'm not sure I understand how this is relevant to
Access->MyODBC->MySQL, since that's a connection between MySQL
running locally to a remote instance of MySQL. Right?


In fact, my first hint of this was that the ASP connection is in
fact an external connection via a server. Here is my Connection
string (Personal info kludged of course):
dbConn = "DRIVER={MySQL ODBC 3.51 Driver};" & _
"Server=mysql.brinkster.com;" & _
"Database=mydatabasename;" & _
"Uid=myuserid;" & _
"Pwd=mypassword"

I entered the same info in the connection for MyODBC and it works.
I linked to the tables from the Access App using the MyODBC
driver. I have NO REASON to lie about this. In the face of this
you should apologize to me. I am not a lier.


Well, if you can do it then it shows that your ISP has opened up the
port to make it available across the Internet.

I would run as fast as possible from a host that did this by default
and publicized the port number. It just isn't safe to expose
database ports to the open Internet.

But it does appear that your host is doing it, so I retract any
accusation of fabrication.

But it isn't something I'd ever consider as a viable and secure way
for deploying an application.

The name of the server, the port number, and the name of the database for my databse are only available to me. It is listed in the admin area of my account maintenance. Each user will have a different combination, and all database names are unique on the system. The example states that the actual names are not the same as what they use in the example, they do not publisize the actual info anywhere except in my admin area. AFAIK, This is as secure as any external connection can be. They host thousands of these databases and thousands of the other types (Jet and SQL Server). In fact you can signup for their free account and get ASP and Access(Jet) support. I've been using them for 6 years without any problems. BTW, the Access(Jet) connection is via the ASP variable Server.MapPath(pathToDatabase) so there seems to be no external connections there. The documentation on the SQL Server points to a server just like MySQL.

Apology accepted.

--
Bri

.

Relevant Pages

  • Re: SQL2005: Cannot connect error 11001
    ... user mapped to one database. ... Does the issue has to do with the login account / user ... Server connection. ... if you changed the port ...
    (microsoft.public.sqlserver.connect)
  • DB Fault Tolerance - network connections
    ... a Perl server which talks to a PostgreSQL database on a different phys. ... block the port on the DB server, ... Note that I'm using iptables on the box that is running the Postgresql ...
    (perl.dbi.users)
  • Re: Created on Access 2003, but.......................
    ... But that's not secure under any scenario, as any port scanner ... Well, you still need a userid, password and database name. ... You're assuming the server remains in a secured configuration. ...
    (comp.databases.ms-access)
  • HttpHandlers on a website NOT using port 80
    ... The content is stored in a database. ... The problem is that we have changed the development server where the editing ... a subweb of the Default Web Site (port 80). ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Created on Access 2003, but.......................
    ... fact an external connection via a server. ... the port to make it available across the Internet. ... But it isn't something I'd ever consider as a viable and secure ...
    (comp.databases.ms-access)