>>>i used to make projects with several tables all in one database. regularly i would have problems with validation of databases for various reasons. it was solvable but my intervention was always necessary.
>>>
>>>recently i made a project using free tables instead of putting all into the database.
>>>
>>>i found no change in speed or the way i programed or in the way i used my SQL commnands.
>>>
>>>so my question is what is my advantage of using the database in the first place (other than being able to use more than 10 characters as a table name).
>>>
>>>i found using free tables a lot easier with more peace of mind.
>>
>>Referential integrity is the most important argument.
>>
>>Apart from the arguments presented by Terry, a free table can't participate in transactions.
>>
>>Also: I find it very useful to have field comments. This is not possible with free tables. With comments, the documentation is included in the database structure itself, which is very useful.
>>
>>Grüsse,
>>
>>Hilmar.
>
>Damn! And I forgot Persistant Relationships and the ERD!


Database is also dictionary which you had to build yourself back in dos times.
Data about our data. It could hv had few more empty fields (other then comment) for us to use, but in general they are quiet good.

Point about buffering/transactions is quiet important. Wish VFP was supporting transactions across multiple databases, but even without it
it can still safely manage huge quantities of data, provided that
applications are solidly built.