The SQL statements in Access execute on the user's machine, not on the
machine containing the remote database. Access is a file-server database,
not a server database. Further, you can't use ODBC to connect an Access
front end to a Jet database (which is what you have, but often called
"Access" because it is the default database engine that comes with Access).
You might be able to do that using some other Office software for the
front-end... Excel, perhaps (though I have not done so).
As a file-server database, it uses the remote database folder just as it
would if it were on the local hard drive. It doesn't "bring the whole
database across the network" but it does do "every I/O that it would do to
the local hard drive".
I have a colleague who "turned Jet into a server database" for very specific
use, by coding a VB app accessing Jet on the server, and a VB application on
the clients that only sends messages back and forth to the VB app on the
server. But this was on a LAN, too, not on the Internet. The same approach
might work over the Internet, I suppose.
But the fact is that it is just not feasible to use an Access front end with
an Access/Jet database containing the data via the Internet. I'm sorry but
that's the case... Access just is not a server database like the MSSQL,
MySQL, and PostgreSQL you cite.
Larry Linson
Microsoft Access MVP
"Greg Gursky" <ggursky@see.signature> wrote in message
news:3f614d52$0$68323$45beb828@newscene.com...[color=blue][color=green]
> >If you'll clarify with more detail about what you need to do, perhaps
> >someone can make a suggestion. Please clarify here in the newsgroup, not[/color][/color]
by[color=blue][color=green]
> >e-mail. Thanks.[/color]
>
> Thank you for the response, Larry. Unfortunately remote
> control and VPN solutions are not an option. In my case I'm
> writing a front end application that needs to read data from
> the database across the internet. I assume that since Access
> is a relational database, one can make table queries as with
> SQL databases. This is, at least initially, all I need to do, basic
> SELECT and SHOW queries and the like. If possible, I'd like to
> use ODBC to query his database but it must not conflict with
> the DAO transactions being performed constantly by his web
> server.
>
> Honestly, I think he's using Access in a situation where a
> full blown SQL server is called for, but I have no control
> over that. I need to work completely within the boundaries
> of his current setup. I will never have access to his server
> and doubt I could convince him to change anything
> significantly.
>
> As I mentioned, I've never used Access, so I might be
> completely off base here. I'm basing this all on my experiences
> with ODBC and SQL servers like MSSQL, MySQL and postgreSQL.
> Any further help would be greatly appreciated.
>
> Thank you,
> Greg
>
>
> --
> Greg Gursky
> Bitspring
>
ggursky@bSiPtsApriMng.com (remove SPAM)
>
http://www.bSiPtsApriMng.com (remove SPAM)
>[/color]
