I have created a database and I need a "front end" to allow others to update/view the database. The "others" do not have Microsoft Access. Is this possible to do?

Hi Hecrowell

Yes you can split your database into a front-end and back-end (the back-end being on your server and containing only the tables, the front end is then put on each workstation and has all the queries, forms, reports macros and modules). However, if you wish to achieve this without the workstations having a copy of Access installed, then you will need to purchase the Developer's Version of Access (which will allow you to install a run-time version of Access as the same time as installing your database but keeping you and your users inline with software registration).

HTH

Rich

I have had major grief with Access runtimes in the past however a company named SageKey have addressed most of the (very real) problems.

Heres some figures to think about
the Access 97 runtime, without any options, loads 56 files and creates 1,097 registry entries

Anyone who has tried to distribute Run time Access Applications should Read this article
http://www.sagekey.com/article.htm

I have a list on My site of the runtime files required for an Access 97 Runtime. These do not include the Files required to install the Runtime. The list can be found at
http://www.accesswatch.co.uk/html/access_developer_file_watch_97/access_developer_runtime_file_watch.html

Distributing Access Runtimes can be difficult and/or expensive. However SAGEKEY appear to of taken most of the hard work out of this (I have not used the product but have heard good things about it). You will still need the Developer's Version of Access because this gives you the License to distribute an Access Application.

In broad terms, for a succesful distribution, You require:
Native Access (To build your Application)
Access Developers edition (For runtime License)
3rd Party Installer-InstallShield - Wise Etc(Better than the MS Supplied Installer)
SageKey Script to take out the hastle.
Sagekey can be found at http://www.sagekey.com/

I'm not trying to put you off but am trying to indicate the level of commitment required to distributing Access runtimes. The article
above indicates most of the problems in some detail

An alternative to distributing Access Runtimes is to Use Visual Basic with Access Tables. This topic has been covered a number of times on this forum so use the forum search for further details

Hope this helps
Regards
Trevor From www.accesswatch.co.uk (http://www.accesswatch.co.uk)