>Thanks all for your replies.
>
>The impression I'm getting is that conversion could be enough hassle to maybe side with a language that has a more predictable future.

My very (sad) point.

> Speed is a problem though as we have tables with 1million+ rows.
>
Seems a lot of rows to me. You will, but I have no experience here, probably benefit from the introduction of a DBMS.

>Commit/Rollback is implemented with VFp is it not?

Yes. It works exactly as you would expect it. I have had very good experiences with it.
>

How is this implemented? Is this purely on application level or db level?

Not sure I understand the question. You BEGIN/END TRANSACTION and ROLLBACK in code of course, but all the rest is take care of at the .DBC level.

? To what extent is VFP more relational than fp26.

How more relational can you be than fp26? :). That being said the dbc (read the DBMS) has added functionality, RI (relational integry) checking, stored procedures etc. I personally have stayed away from it because I have my doubts about conveying code to a .dbf file (read the .DBC), but I hear that a lot of people use it and are happy with it. There is also some support for an embryonic datadictionary, but it takes one to want to see that way :).


Regards.

Marc