F
Fred
I hate to say this on such an interesting discussion (and also admit that I
haven't fully absorbed what's in all 27 postings) but, may I suggest the
following 30,000 ft. view idea. But I know both music and databases and
math.
Chords are basically mathematical formulas:
note #1 = ?
note #2 = ?
note #3 = ?
note #4 = ?
except that the inputs and ouputs are translated from and to other
terminology (Scales, Chord types and notes) And there are a lot of
different simple equations. A table can be used to store the equation for
each cord
And in databases you don't store the results of equations, your execute them
at the time that you want to see the data.
Sincerely,
Fred
haven't fully absorbed what's in all 27 postings) but, may I suggest the
following 30,000 ft. view idea. But I know both music and databases and
math.
Chords are basically mathematical formulas:
note #1 = ?
note #2 = ?
note #3 = ?
note #4 = ?
except that the inputs and ouputs are translated from and to other
terminology (Scales, Chord types and notes) And there are a lot of
different simple equations. A table can be used to store the equation for
each cord
And in databases you don't store the results of equations, your execute them
at the time that you want to see the data.
Sincerely,
Fred
Rog said:Understood... I'm doing that now. The problem is that for some reason I
cannot get the resulting output to update the subform on the fly - the
result initially shows up in the fields in the subform like it's supposed to,
but if I change the key for exmple, they will only update when I go out of
the form and back in. - not when I make the change.
Also the subform continues to look like a spreadsheet format - that is, even
if I change the subform so that the fields are pretty and colorful, it still
comes out looking like an excel spreadsheet when I execute the query. Why?
I'm getting there, but boy is this grueling! Thanks again.