Hi guys ...
>>>Hello,
>>>
>>>Just a simple question.
>>>
>>>We are having a discussion here at the office about database containers and we would like your input. At the moment one is saying that the database container should be used and somebody else says we can use free tables.
>>>
>>>Can anybody give us the advantages and disadvantages of free tables against tables in a database container?
>>>
>>>Thanks for your time and feedback!
>>>
>>>Greetings,
>>>Michiel Willems
>>
>>Database container allows to use RI-triggers, record/field rules/defaults, primary keys. It's all nice stuff and doesn't cost much to use.
>
>
>In addition, you can only use transactions on tables in a database.
In addition to the addition, you gain long field names (>10 characters) and the ability to use views to access data, which gives you future scalability.
There simply is no compelling reason *not* to use a database container. If I recall, Michiel, aren't you the guys trying to put together a framework? If so rely on always using a database container if nothing else than to keep your options open.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05