>Why not just use native Jet tables, creating new tables, fields, and views when you need them via parameter driven code that builds/executes the appropriate SQL statements. IMHO much more powerful/flexible, and with reduced query overhead, too!
SQLNotes aim is not to compete or replace MS Office apps, but to complement. Some applications are best served with MS Access, some with Excel, some with Word. Some with SQLNotes. Many reasons not to use straight tables:
1- As the data represents a "sparse matrix", this would not be efficient
2- Max of 255 fields in JET 4.0
3- Granularity: changes to invididual cells could not be tracked, dated, by who, etc
4- Multi-user: add/remove fields would require table locks. Record locking would prohibit updates to different cells of a given record.
5- Integrity: file-based databases tend to corrupt data, especially for records with many fields. Having 1 field per record works around this limitation.
6- For large number of fields with sparsely filled records, it may even be faster to do it the SQLNotes way.
7- It is not that different from column-oriented databases: http://en.wikipedia....Column-oriented_DBMS
(in particular the Benefits section)
8- I have databases with 30,000 items, 400,000 field values, >200 fields and response times is still excellent event with 8 connected users.
9- Much easier search. Searching all occurences of a given text string requires a single SQL query on a single field.