You are restricting yourself quite a lot if you use free tables.

For one, you can't use triggers; this also prohibits referential integrity.

Also, free tables can't participate in a transaction.

For views, however, I think you can define them in a database, and still access free tables. It is only the view that has to be defined in the database.

Views can also be defined programmatically, but that is much more complicated than defining them in a database. Also, I am not sure whether they still have to be linked to a database, or whether they can be defined "standalone".

I recommend a database, at least for the views.

>Hello Jaime,
>
>Thanks for the answer. I presume the views have to be defined in the DBC? Is that correct?
>
>Since I use free tables, I'll try with a Cursor Adapter.
>
>Thank you.
>
>Alex
>
>>Alejandro
>>Yes and Yes.
>>Although editing directly into the grid is not a behavior i would recommend, you could answer Yes to both your questions just by using local/remote parametized views. You can, in your view definition, specify what fields are updatable, and you can, in this manner, show data from different tables, and update this data into all the different tables at the same time.
>>
>>Jaime
>>
>>
>>>Can you reliably make a grid show data from different tables that are related? How about edititng the data?
>>>
>>>I believe not, but ask just in case (it would be convenient).
>>>
>>>TIA,
>>>
>>>Alex