Good evening.
I think it's important to understand that you really have TWO distinct components to this database.
First, you have the Database Engine itself. That's the component in which the data is stored. The database engine in Access is called ACE. MySQL is another database engine. Both would fill the same role for you, but MySQL is likely to be more effective behind a website.
Second, you have the interface, i.e. the "screens" or "pages" that you display to the users. They provide a way to add new records , update existing records, delete records, and-to the requirement you have here-report on existing data. Access is a very fine tool for creating interfaces that will run on the desktop as Windows clients. However, Access itself does NOT run in a web browser. I'll get back to that point later.
If you choose MySQL, you'll be faced with the same issue-you'll need to create the interface as web pages for your users. It simply doesn't have any tools for creating the interface.
Office 2010 DOES have the ability to create web-enabled databases which do run in a browser; however, they run only on a SharePoint server which offers what is called "Access Services" to support those databases. Hosting services, like AccessHosting.com, offer monthly subscriptions for this service. If this sounds interesting to you, I think you're proposed application is simple enough to fit that environment. However, the hosting costs will be greater than on an "old-fashioned" hosted website.
"My webhost says I can upload an MDB file and users will be able to use it as if the database resided on their own computer." That statement is vague enough to be true given certain qualifications, and, at the same time, quite possibly misleading. What I would like to know, before I committed to that path, is exactly what they mean by that.
I am not aware of any specific templates for this particular type of database, but what you've described so far is reasonably simple. If you are NOT allowing users to update, delete or add records, it should be quite straightforward.
You'll need to create a table of diseases and a table of microbes.
Then you'll need a third table to record relationships between microbes and diseases.
And finally, you'll need a table to record relationships between diseases and other diseases.
The interface through which you do the querying can be created with a set of drop down boxes at the top, one for each of your searches. The results can be displayed in a grid below them. That can be a list box populated by a query returning your results, or it can be a subform.
HTH
George
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of tryggvi@sbcglobal.net
Sent: Monday, July 11, 2011 11:26 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Medical database
I want to put a medical database on a website. My webhost says I can upload an MDB file and users will be able to use it as if the database resided on their own computer. I want users to be able to do three things:
1. Type in the name of a disease and get a list of related diseases
2. Type in the name of a disease and get a list of associated microbes.
3. Type in the name of a microbe and get a list of associated diseases.
I have Access 2007, but I haven't built a database in 15 years. My data is currently in MS Word tables.
I would like to know if Access 2007 is a reasonable choice for this project (MySQL is another option), and if there are templates that will make the task easier. I haven't built a database in fifteen years and the Northwind Trader's sample database is pretty ovewhelming. Thanks. Russ Farris
[Non-text portions of this message have been removed]
Tidak ada komentar:
Posting Komentar