Building module databases

[rjoseph]

Does anyone have a technique for developing a main database that could then have modules added to it at a later time without modifying the main database. The added database needs to integrate well with the old main. An example of this is a database of movie titles with summaries that you later decide to add movie reviews to. Thanks in advance for your help.

[Chuck]

quote:

---

Originally posted by rjoseph:

Does anyone have a technique for developing a main database that could then have modules added to it at a later time without modifying the main database. The added database needs to integrate well with the old main. An example of this is a database of movie titles with summaries that you later decide to add movie reviews to. Thanks in advance for your help.

---

I don't know of a really easy way to do this, but one thing you can do to make it easier to add databases to the system is to make each database have a record in the main file. The button to take a user to that database is just the record in a list view (formatted to give a good interface). The script that runs checks to see the contents of the "Database Name" field, and runs different scripts depending on which record the user was in.

But there's still going to be a lot of work to do to integrate it with the rest of the system. But at least it's one thing to make it a bit easier.

Chuck