Other
technologies do however support http:// connections such as SQL server and
My
Sql, but they do so with server apps.
Yes, and ms-access also supports the above types of connections also.
The problem is not ms-access, it is your internet, and your providers.
You can most certainly use ms-access with sql server, or mysql. In fact, the
last 3 versions has included a desktop edition of sql server for free with
ms-access. This data engine, or sql server, or oracle, or mysql can ALL BE
USED without ms-access.
For the app I am working on, unless I can programmatically set up a VPN,
then this solution is just not portable enough.
And, why not use a server based system, and continue to use ms-access for
the interface? (that is what most of us do, and was one of my suggestions in
the link).
Ms-access is not the database system. You can't build a form, or interface
in MySql, but you most certainly can in ms-access!
So, ms-access is the interface building part, and the choice of a database
engine can range from a file share system (like a mdb file), or a server
based system, like sql server. As mentioned, a free copy of sql server been
included on the last 3 versions of office for use with ms-access.
Not only is the desktop edition free, but also now sql server express. So,
you have a number of free choices for the database part, and ms-access will
work over the internet with these types of data servers.
I mean, you could setup a VPN, but then again, it would be too slow (as my
article points out), and worse, your data file would be subject damage.
However, using a database server solves this problem, and ms-access works
just fine with a database server.