Ooops.
I was almost convinced that allowing multiple instances of the Data class was the right way to go, but then I realized that having static cache and locked record list objects in Data would mean that the Data class could only be used for one database file (table).
On the other hand, only allowing single instances for a given database file and making the cache and lock list instance variables instead of statics means that Data instances could be instantiated for more than one data file (i.e. other data tables).
So the question is (I think): allow multiple instances for greater scalability and possibly greater server responsiveness, or only allow a single instance for each data file but allow Data to be used with muliple data files/tables? If you think growth in the number of users is more important than the first options seems right. If you think that B&S will want to add more tables (a customer table?), then the second option seems better.
I'm leaning back towards single instances and so allowing multiple tables in the future. I'm also just rambling now. Any opinions on this?
Regards,
jb
P.S. I noticed I'm now a "ranch hand"
I was curious how this came about.