We have a fairly large, complex Access database with lots of forms and queries.

I need to allow other users who are not on the network to view, add and edit data.

I could build it all in ASP but that would take a while and seems a shame when all the forms etc are already done and working.

Is there a way I can distribute a front-end version of this database with just the forms to our remote users, and have that database look online to get the back-end data. We have web space already set up; our host also allows us to get sql server space, although ideally I'd like to link to another online Access database.

Thanks in advance for any help

Graham

If all of the people needing access from the outside are trusted sources, wouldn't it be easiest to set up a VPN rather than rent web space? Though I wouldn't know if that is fast enough for what you are trying to do.

Thanks emgeh. Yes, we've been looking into the vpn option, but I also need to know the alternative i.e. if we can make it work with a light access front-end connecting to remote table data, be it access or sql server.

This is interesting because we have to also make this choice for our company but we thought that in sheer cost terms, VPN cannot stand out against web space together with that of Broadband. Besides, in places like China, VPN is not available in all the areas. So web space makes more business sense?
I would like to know more about these two choices
Thanks&regards
Rao

Another option would be to save the Database in a directory on an FTP server, then have those people who will be offsite use an FTP to drive utility (maps an FTP location to a local drive) & use the database as normal. I would however suggest at least having an SSH tunnel for this to pass over (Putty on the remote machines & a linux server at the host with SSHD & FTPD running), this will provide a moderate amount of security. One issue that may arrise is the file locking that MS Access likes to perform. Another problem would be latency, as MS Access was designed to be used by a single person at a time on a single machine (later expanded to work in a network environment). This results in many menial requests back and forth. The next step up in reliability would be VPN (latency issues will still be present for the same reason as the previous suggestion). The best option (for both speed and reiliability is putting together a web server which transfers the requests to the database through ODBC connections). This last option also provides the best solution for growth because a single web server can (depending on configuration) respond to hundreds or thousands of simultaneous requests with minimal impact to the backend (the database). As the utilization of the database increases you can also see about converting from access directly to an MS SQL database (there are utilities out there that will perform this function). Additional performance gains can be realized by this last conversion.

On a side note by using a web server you can also easily implement security through the use of SSL.

Can you suggest some FTP to Drive utilities that could be used? Preferably freeware!!

Thanks

Mike
EchoVue.com