Putting my Access 97 database on the web

[Rebecca]

I have a large Access 97 database that's been split into a front and
back end. We've used it successfully with several computers networked
together, but now some of the people in my organization are saying that
since some of the people who need to get at it are all over the state,
it would be nice to put it up on the web and have a web interface for
it. Is there any way to do this without rewriting the entire front end
in some other language? Much of what the database does is written into
the VBA code.

Thank you for any insight you can give me,
Rebecca

[Pavel Romashkin]

As far as I know, no.
I am going the path of implementing a limited FE functionality in ASP. I
will leave full VBA FE functionality for those who choose to work in the
main office :-)
Pavel

Rebecca wrote:

I have a large Access 97 database that's been split into a front and
back end. We've used it successfully with several computers networked
together, but now some of the people in my organization are saying that
since some of the people who need to get at it are all over the state,
it would be nice to put it up on the web and have a web interface for
it. Is there any way to do this without rewriting the entire front end
in some other language? Much of what the database does is written into
the VBA code.

Thank you for any insight you can give me,
Rebecca

[Rebecca]

Thanks for replying. I thought that maybe that was the case. It's true
that only one person (for now, anyway) really needs the majority of the
functionality of the db. All the others will only be working with the
one table and a few other small tables that relate to it and not much else.

How is ASP to work with? What's the easiest way to learn it? Do you
have a recommendation for a book or site?

Thanks,
Rebecca

Pavel Romashkin wrote:

As far as I know, no.
I am going the path of implementing a limited FE functionality in ASP. I
will leave full VBA FE functionality for those who choose to work in the
main office :-)
Pavel

Rebecca wrote:

I have a large Access 97 database that's been split into a front and
back end. We've used it successfully with several computers networked
together, but now some of the people in my organization are saying that
since some of the people who need to get at it are all over the state,
it would be nice to put it up on the web and have a web interface for
it. Is there any way to do this without rewriting the entire front end
in some other language? Much of what the database does is written into
the VBA code.

Thank you for any insight you can give me,
Rebecca

[paii]

You could put the application on a Terminal server or PCAnyware computer,
then allow your remote user to connect though a VPN.

"Rebecca" <Re*****@JaxonF amily.net> wrote in message
news:uIBgb.6960 64$YN5.568014@s ccrnsc01...

I have a large Access 97 database that's been split into a front and
back end. We've used it successfully with several computers networked
together, but now some of the people in my organization are saying that
since some of the people who need to get at it are all over the state,
it would be nice to put it up on the web and have a web interface for
it. Is there any way to do this without rewriting the entire front end
in some other language? Much of what the database does is written into
the VBA code.

Thank you for any insight you can give me,
Rebecca

[Saintor]

Among others, three easy possibilities;
- Learn Frontpage
- Use www.genericdb.com
- If it is limited to few people, the use of Windows Terminal Service (the
easiest, IMO).

"Rebecca" <Re*****@JaxonF amily.net> wrote in message
news:uIBgb.6960 64$YN5.568014@s ccrnsc01...

I have a large Access 97 database that's been split into a front and
back end. We've used it successfully with several computers networked
together, but now some of the people in my organization are saying that
since some of the people who need to get at it are all over the state,
it would be nice to put it up on the web and have a web interface for
it. Is there any way to do this without rewriting the entire front end
in some other language? Much of what the database does is written into
the VBA code.

Thank you for any insight you can give me,
Rebecca

[Rebecca]

That's interesting. Would it then behave just like it would on a local
network? Is it secure? Expensive? This is a not-for-profit
organization without a lot of excess in their budget.

Rebecca

paii wrote:

You could put the application on a Terminal server or PCAnyware computer,
then allow your remote user to connect though a VPN.

"Rebecca" <Re*****@JaxonF amily.net> wrote in message
news:uIBgb.6960 64$YN5.568014@s ccrnsc01...

I have a large Access 97 database that's been split into a front and
back end. We've used it successfully with several computers networked
together, but now some of the people in my organization are saying that
since some of the people who need to get at it are all over the state,
it would be nice to put it up on the web and have a web interface for
it. Is there any way to do this without rewriting the entire front end
in some other language? Much of what the database does is written into
the VBA code.

Thank you for any insight you can give me,
Rebecca

[Albert D. Kallal]

Well, there is certainly a cost. However, that cost is often much less then
re-writing the part and the cost of setting up a web server.

If you are running windows 2000 server edition, you can enable remote
access, and anyone anywhere on the internet can use the application. You are
allowed two free remote users at the SAME TIME. If you need MORE THEN two
remote users at the same time, then you have to start shelling out some
money.

I would also of course for reasons of security use a VPN. Regardless,
setting up your own web server, or terminal server does requite someone with
experience in these areas (TS is way easier to setup then a web server
anyway. And, you don't have to change, or re-write your application).

For some reading on this issue, you can read the following of mine:

Using a wan with ms-access? How fast, how far?
http://www.attcanada.net/~kallal.msn/Wan/Wans.html

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn

[Pavel Romashkin]

Nice simple article, Albert! The sensitivity of file share mode to
dropouts on the netowork is exactly why I feel that the VPN is not a
good idea and if one wants multi-user, wide area access, they should use
a client-server approach.
I would like to add that to deploy a small database it is not necessary
to set up a web server. There are tons of commercial providers out there
with IIS deployed who will sell you web hosting with SQL server / Access
DB (OLEDB, ODBC) support for $10-100 a month, depending on the space and
reliability requirements.

Cheers,
Pavel

"Albert D. Kallal" wrote:

Well, there is certainly a cost. However, that cost is often much less then
re-writing the part and the cost of setting up a web server.

If you are running windows 2000 server edition, you can enable remote
access, and anyone anywhere on the internet can use the application. You are
allowed two free remote users at the SAME TIME. If you need MORE THEN two
remote users at the same time, then you have to start shelling out some
money.

I would also of course for reasons of security use a VPN. Regardless,
setting up your own web server, or terminal server does requite someone with
experience in these areas (TS is way easier to setup then a web server
anyway. And, you don't have to change, or re-write your application).

For some reading on this issue, you can read the following of mine:

Using a wan with ms-access? How fast, how far?
http://www.attcanada.net/~kallal.msn/Wan/Wans.html

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn

[paii]

The application is running on the local network when using Terminal server.
Terminal server CALs cost $60 per user, if you already have Windows 2000
server.

"Rebecca" <Re*****@JaxonF amily.net> wrote in message
news:T4Fgb.6971 49$YN5.568509@s ccrnsc01...

That's interesting. Would it then behave just like it would on a local
network? Is it secure? Expensive? This is a not-for-profit
organization without a lot of excess in their budget.

Rebecca

paii wrote:

You could put the application on a Terminal server or PCAnyware computer, then allow your remote user to connect though a VPN.

"Rebecca" <Re*****@JaxonF amily.net> wrote in message
news:uIBgb.6960 64$YN5.568014@s ccrnsc01...

I have a large Access 97 database that's been split into a front and
back end. We've used it successfully with several computers networked
together, but now some of the people in my organization are saying that
since some of the people who need to get at it are all over the state,
it would be nice to put it up on the web and have a web interface for
it. Is there any way to do this without rewriting the entire front end
in some other language? Much of what the database does is written into
the VBA code.

Thank you for any insight you can give me,
Rebecca

[Rebecca]

Is it reliable? I went to the site that Albert Kallal suggested (above)
where he discusses it, and he suggests that since the VPN is subject to
occasional disconnects, the database can be corrupted. What do you
think about that? Of course, I don't want that to happen, but a VPN
does seem like the perfect solution otherwise.

Rebecca

paii wrote:

The application is running on the local network when using Terminal server.
Terminal server CALs cost $60 per user, if you already have Windows 2000
server.

"Rebecca" <Re*****@JaxonF amily.net> wrote in message
news:T4Fgb.6971 49$YN5.568509@s ccrnsc01...

That's interesting. Would it then behave just like it would on a local
network? Is it secure? Expensive? This is a not-for-profit
organizatio n without a lot of excess in their budget.

Rebecca

paii wrote:

You could put the application on a Terminal server or PCAnyware
computer,
then allow your remote user to connect though a VPN.

"Rebecca" <Re*****@JaxonF amily.net> wrote in message
news:uIBgb.6 96064$YN5.56801 4@sccrnsc01...
I have a large Access 97 database that's been split into a front and
back end. We've used it successfully with several computers networked
together, but now some of the people in my organization are saying that
since some of the people who need to get at it are all over the state,
it would be nice to put it up on the web and have a web interface for
it. Is there any way to do this without rewriting the entire front end
in some other language? Much of what the database does is written into
the VBA code.

Thank you for any insight you can give me,
Rebecca