I'm in the process of designing an accounting application that will be commercial in nature.
This will be a multi-client system, that is, the user will be able to create a database for each client that they want to maintain with the system.
I need to have some system tables to store information about the various tables created so that I can, for example, display a list of all databases that were created; as well as information about the client data contained in those tables. This will be presented as a "client listing" that they can select from and then proceed with doing processing on the selected database.
I will also need a separate, but duplicate, database for each client that they want to maintain data for. When they initially start the system, a default (or sample) client will be selected. From that point, they can create new databases or select another one from the client listing.
I know this is very brief, but I think you get the idea. My question is has anyone created a system like this and can you provide any insight into the general layout design that I provided above?
Some might think it would be easier to put all the clients in one database, but this is impractical because each client's data has to be moveable. The user may need to copy the database to their laptop to take to the client's office to do some processing.
This will be a multi-client system, that is, the user will be able to create a database for each client that they want to maintain with the system.
I need to have some system tables to store information about the various tables created so that I can, for example, display a list of all databases that were created; as well as information about the client data contained in those tables. This will be presented as a "client listing" that they can select from and then proceed with doing processing on the selected database.
I will also need a separate, but duplicate, database for each client that they want to maintain data for. When they initially start the system, a default (or sample) client will be selected. From that point, they can create new databases or select another one from the client listing.
I know this is very brief, but I think you get the idea. My question is has anyone created a system like this and can you provide any insight into the general layout design that I provided above?
Some might think it would be easier to put all the clients in one database, but this is impractical because each client's data has to be moveable. The user may need to copy the database to their laptop to take to the client's office to do some processing.
Comment