Needed: A Relational Database for Normal People

I cant be the only person on the planet who needs to create a database that encompasses many-to-many relationships, but isnt a professional database designer. Yet, I have not found anything that makes building such an application terribly easy for people like me.

For example, when I organize a conference I do a database of the speakers and the sessions. Id like to be able to connect them, showing which speakers are presenting at which sessions. This shouldnt be so hard—when I tell you what I need you understand it immediately. I need a database that can link speakers to sessions and vice versa, allowing each change in one to show up in the other.

Now this is merely difficult if each speaker is only presenting at a single session. Sadly, thats never the case at my events. Linking speakers to multiple sessions has thus far proven more trouble that its worth.

Are you outsourcing your database? Read about its risks.

Put another way: I dont think I should have to read a database book or take a class to build the app I need. I shouldnt have to understand the ins and outs of normalization and key fields to make this happen. Handling these relationships is something the database itself should know how to do with limited help from me.

FileMaker 7 comes closest, but simple as it is generally, the relationship-building process still requires more database knowledge than most users, even power users, possess. I cant just sit down with an idea for an application and just build it. FileMaker is a fine product, it just doesnt do what I need.

Intuits QuickBase is an online software-as-a-service environment that makes building even applications pretty easy. But like all the other databases, when you need relationships things get complex. QuickBase does one-to-many relationships with some difficulty, but doesnt even try many-to-many connections.

Next Page: If I were king ...

Next: ' Page 2 ' >>