MS Access - runtime?

[Mark Sullivan_3]

This is my first time delving into Access for support issues. I have a user who is writing an Office XP Access database. She has asked that Access be installed on 15 other PCs so that other users can enter and edit the data. They dont need to make any design changes. This, I believe, is a little over the top and costly.
1. Am I right in saying that MS Access runtime would overcome this problem.
2. How is it implemented
many thanks in anticipation
Mark Sullivan
PS - I'm a great beliver in awarding points!!

[Ron Kinner]

Mark,

Certainly appears that that is the case.

"If you build an Access database (.mdb) as the front-end application, you can deploy the database to users who do not have Access on their workstations by distributing it together with the run-time version of Access. The Access Runtime is a version of Access for which certain features have been disabled, including the ability to create and modify databases."

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/modcore/html/deovrdeployingaccesssolutions.asp

I'm glad you asked the question. I didn't know about the runtime version and I have a similar situation where the users would be better off not having the ability to mess with it.

Ron

[Mark Sullivan_3]

Thanks Ron,
Pointed me to exactly where I needed - Hope it helps u 2
cheers
Mark S..

[Jon Finley]

Another way to address this is to use ODBC or FrontPage components, and build a web interface to access the database. Fairly easy to do, and you can use either ASP or CGI pages.

FrontPage can natively manipulate Access (using ASP pages). With fairly little work, you can have a page or pages that can be accessed worldwide, limited only by whatever users or groups you permit into the site or page.

Jon

[Mark Sullivan_3]

Thanks for the info Jon,
I have already got the Office Devlopers package so I'll try down the route suggested by Roy - thanks very much for the info tho