R
Rob
Hello all,
I have a question about Access2003 and the internet.
I have a front-end/back-end database on Access2003 / windowsXP that works
fine on a locally wired Microsoft network.
Now I want to make it available on the internet.
I have a normal internet hoster that provides me with a webspace, mysql and
php capabilities.
- In order to communicate with the back-end one can build a VPN on the
service provider but using the front-end, the communication with the back-end
becomes extremely slow (tried that: sometimes minutes between mouse-clicks).
- One can create DAP-pages that communicate with MSIE to the back-end mdb.
One needs the Microsoft Office Web Components to be installed , that works
fine locally, but when transporting the mdb and htm with FTP to the distant
server the htm pages do not connect to the mdb.
When I open such an Access-generated htm page in notepad there is a portion
that says:
<a:ConnectionString>Provider=Microsoft.Jet.OLEDB.4.0;User ID=Admin;Data
Source=C:\temp\Mydatabse.mdb;Mode=Share Deny None…….
Obviously, the C:\temp\Mydatabse.mdb should be adapted, but I do not
understand how: simply replacing the C:\temp\ part with my domain name (for
exemple http://www.mydomain.com/Mydatabase.mdb) does not work and the
Microsoft.Jet.OLEDB.4.0 part should be changed to something else?
-I found out that with PHP one should be able to connect to Access with the
[connect_ODBC] php-command. I tried that on the distant server but it does
not recognize this command.
I am no network specialist and obviously, I am missing some important
understanding. Studying the manuals for hours, I came up with nothing helpful.
Can someone explain to me in a few words how it should be done? Which method
is best used with Access and what kind of services a provider should have in
order to connect to Access via the internet?
Any help would much appreciated.
Rob
I have a question about Access2003 and the internet.
I have a front-end/back-end database on Access2003 / windowsXP that works
fine on a locally wired Microsoft network.
Now I want to make it available on the internet.
I have a normal internet hoster that provides me with a webspace, mysql and
php capabilities.
- In order to communicate with the back-end one can build a VPN on the
service provider but using the front-end, the communication with the back-end
becomes extremely slow (tried that: sometimes minutes between mouse-clicks).
- One can create DAP-pages that communicate with MSIE to the back-end mdb.
One needs the Microsoft Office Web Components to be installed , that works
fine locally, but when transporting the mdb and htm with FTP to the distant
server the htm pages do not connect to the mdb.
When I open such an Access-generated htm page in notepad there is a portion
that says:
<a:ConnectionString>Provider=Microsoft.Jet.OLEDB.4.0;User ID=Admin;Data
Source=C:\temp\Mydatabse.mdb;Mode=Share Deny None…….
Obviously, the C:\temp\Mydatabse.mdb should be adapted, but I do not
understand how: simply replacing the C:\temp\ part with my domain name (for
exemple http://www.mydomain.com/Mydatabase.mdb) does not work and the
Microsoft.Jet.OLEDB.4.0 part should be changed to something else?
-I found out that with PHP one should be able to connect to Access with the
[connect_ODBC] php-command. I tried that on the distant server but it does
not recognize this command.
I am no network specialist and obviously, I am missing some important
understanding. Studying the manuals for hours, I came up with nothing helpful.
Can someone explain to me in a few words how it should be done? Which method
is best used with Access and what kind of services a provider should have in
order to connect to Access via the internet?
Any help would much appreciated.
Rob