Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

How to administer an Access database via web-based interface?

Guest
Feb 26, 2010 Feb 26, 2010

There are times when I need to edit a database record to do something my CMS wasn't designed to do, so I have to manually edit it. Normally I just ftp the Access mdb file to my pc, make edits, and reupload the mdb file and hope nobody updated the database in the meantime.  Does anyone know of a web-based database admin system that will allow me to edit Access data?  Sure would be nice if I could install something on the server that would allow me to edit any datasource there and not have to have a separate, customized interface for each datasource.

Thanks for looking, Bill

TOPICS
Database access
770
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Feb 26, 2010 Feb 26, 2010

Make your own personal cf page.  Whenever you need to do something, write the necessary cfquery and run the page.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Feb 26, 2010 Feb 26, 2010

a frightening way to do do it is to expose a page in your app that provides you a text area and a submit button.  Then you can adHoc all night long using any SQL statement your hands can craft.

To that end you can include a dropdown and use it to populate pre-built query templates into the text box.

I would recommend naming that page with an extension that the web server will not serve.  Rename it to use it and then rename it back when done.

D.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Feb 26, 2010 Feb 26, 2010
LATEST

I would recommend naming that page with an extension that the web server will not serve.  Rename it to use it and then rename it back when done.

Or just put access restrictions on it via the web server, so one needs to authenticate to the system before using it.

Or stop using Access and use a decent DB: Access is not appropriate to be used as a DB for a web application.  But that might not be an option.

--

Adam

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources