Kahuna wrote:1. Using Our / Client Servers:
With multiple Clients using the same solution, can I drive Client1 to DBa and Client2 to DBb etc? They can't (with the current structure) use the same CostsTables (and other tables) so diferent DB's are essential.
Yes you can do that with databaseManager.switchServer(). So you switch DB server connection after a user logs in.
Kahuna wrote:FYI: It would be possible to have all Client DB's in one huge structure and 'Filter' only the data for a given (current) DB's data. That would require a fairly dramatic restructuring however and entail a pretty big revision of the current Client data tables , I'd like to avoid that. With our current Clients having 20 , 30,000 records in the main tables and the same in cost files, aggregating several of them (Clients) in one DB would almost certainly cause performance challenges.
30,000 records is nothing for a SQL database. If you are talking
many million rows then you might reconsider.
Just make sure your database is optimized (indices (or not), datamodel) and your database server is optimized.
So in short, yes you can use 1 single code base for all clients and when needed you could use 1 single database and use tablefilters.
Hope this helps.