>No, you're not doing anything wrong. You say just enough about what the data really is to make me curious. There is nothing wrong with that. My data is not classified, but I always think my employer would prefer that I describe it in generic terms, which in my case makes it simpler to discuss. (Dragan once asked if I really did have a table called Things :)

Sounded like a good idea, though. Could make an app more generally usable :). Come to think of it, I've had apps which were quite useful as platforms to build similar things... ahem, apps upon, and it took some imagination to notice the possible similarities (mathematically speaking, the models were isomorphous). I was just lucky that the idea of using the assembly line logic for a restaurant (and stealing some of my code) came in time. If the names of the tables were not so hardwiredly specific about their contents, I'd get the idea far earlier. Now I have a table internally named something like "assembly list" where it actually contains "recipy ingredients" :)