Differences between BDE and TurboDB
Previous  Top  Next


·TurboDB uses its own file format. This means you must convert your tables as described in "Porting BDE Applications to TurboDB".  
·TurboDB does not support SQL servers. If you want to port an application to TurboDB that uses BDE to access a SQL server you have to create TurboDB table files for your data as described in "Porting BDE Applications to TurboDB".  
·TurboDB does not support some of the field types available with the BDE. These field types are: ftWord, ftCurrency, ftBCD, ftParadoxOle, ftDBaseOle, ftTypedBinary, ftCursor, ftFixedChar, ftWideString, ftLargeint, ftADT, ftArray, ftReference, ftDataSet, ftOraBlob, ftOraClob, ftVariant, ftInterface, ftIDispatch, ftGuid  
·The SQL dialect used with TurboDB (called Turbo SQL) does not provide for outer joins. See "Turbo SQL vs. Local SQL" for details.  
·Field names have to be valid identifiers. Some examples of invalid field names are "#", "2", "Name with spaces"  
·There is no TSession object with TurboDB components. Like dbExpress and other Delphi database technologies TurboDB uses connection objects (TTdbDatabase) for managing the connection.  
·You can use only one TTdbDatabase object per application, because TurboDB is not multi-threaded.  
·The localization support of TurboDB works with custom link libraries.