Andrew Jensen wrote:
... Finally, there should be some mention of the fact that Base is not actually married to the embedded HSQLdb engine at all. The fact that it ships with this is more a matter of convenience, the design of the module is such that additional database engines could be supported in both embedded and in client / server environments. Not to mention the support for working with a spreadsheet as a data store, text files and dBase files. In each of these cases the Base data type will map to slightly different data types in the engine. Perhaps though this is better left for an advanced treatment. ...
Are there any plans to include a section comparing, in practical terms, which database type to choose for some typical projects?
E.g. if you need a database that's a single file and can be easily e-mailed to another office, you probably want the embedded engine (HSQLDB for now).
Or, if you need a database that can be easily edited or massaged en mass, a spreadsheet might be the best option (if you can live with the no-update bug).
Or, if you have 500,000 records, to be accessed concurrently by 20 employees, you probably don't want to use csv files.
This is a critical choice that the current UI gives almost no help with. It then falls to written documentation to explain the concepts and assist in choosing the right one.
<Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
