Nah, they can't, afaik. That's why I was looking for something that might simulate them.

>Unfortunately, I don't believe that free tables can participate in a transaction in VFP 7. That feature was added in VFP 9.
>
>I tried to do something to simulate transactions for free tables in VFP 6 for a similar scenario and was never able to come up with a satisfactory answer.
>
>
>>>>No great biggie here.
>>>>
>>>>I'm replacing a system from its FPD26 days, and the tables still need to be used by the old system. There are cases where there's a 1-m reln. so as I create a certain rec I need to create < = 3 related table recs. I'm afraid of crashes during this process, or during my programmed cascaded delete
>>>>
>>>>I was wondering if anyone knew of, or has developed a clever way around the fact that you can't use transactions here, as the old tables aren't part of a dbc. The only way I can think of is to keep track of newly created recs and deleting them if, say, a related TableUpdate() fails, or say, using RECALL when part of a cascaded delete fails.
>>>>
>>>>'ppreciate it
>>>>
>>>>Terry
>>>
>>>Terry,
>>>If the old system would continue to use them then you already would access via a view, no? There is a dbc IOW.
>>>Cetin
>>
>>Sorry, Cetin, I don't follow you. I don't access the tables as views - just as tables. Non-dbc tables don't support views do they, or am I missing something here.
>>
>>Whatever, how can I use xactions?