There are many things that a database and an orchestral symphony have in common. While I was studying music in college, my job was databases, so I've been thinking about these two topics together a bit for 25 years, but haven't talked about them together.

Parallels exist from the perspectives for both the creator and user/listener. They range from design elements to linear vs. non-linear experience, movements, layers, and textures. We'll listen to examples from Mozart, Beethoven, Mahler, and Gorecki, and contrast these works to FileMaker databases.

These are some symphonic terms that find relevant to database development:

• The Symphonic Form, and how it has evolved (the Graph)
• Baroque/Classic/Modern/Impressionistic/Post-Modern (Pre/post FM7-think, calc vs. script, etc.)
• Symphonic Movements (database modules)
• Structure, harmony and rhythm (core user interface)
• Layers, texture & orchestration (stylistic user interface)
• Leitmotif (small things | loosely joined™)
• Repeated partial linear experience (listening to parts of the same work repeatedly = using a database)
• Time and effort to compose a symphony similar to creating a database

The goal is not just to discuss the theory, but to become better FileMaker developers by bending our minds around database terms through the lens of music. Whether you know anything about classical music, this session will hopefully examine a new perspective on how users experience databases, and how developers experience writing them.

---

I need help! Please send me files that illustrate these concepts. Please send interface screen shots, scripts, graph and structural examples, musical examples, or anything you find interesting to matt@msnmedia.com