Best Way for Dynamics Layouts?

[Dave Hage]

Daer All,

I have an film cue project database I am trying to build. I am new to this (I am a music copyist). I am wondering if this is possible?

I have a database of music cues, each cue has an orchestra size (2 Flutes, 2 Oboes etc) related to it. One project will probably have 3 or 4 different orchestra sizes. Can I have one layout that will list cues in each different orchestra, without showing fields that don't exist for that particular orchestra size. For example A orchestra has 3 Flutes and B Orchestra has 2 Flutes, how do I hide the Flute 3 field for B orchestra. I am trying to avoid building dozens of layout,s one for each orchestra size. Any pointers in the right direction gratefully received.

Regards

Dave Hage

Dakota Music Service Ltd

[transpower]

I think you need three tables: Orchestra, Cue, Instrument. The Cue table will link Orchestra and Instrument.