Massimiliano wrote: >It seems that using TDISqlite3UniDirQuery recordcount is every time = -1. This is correct. >Do I miss something? TDISqlite3UniDirQuery is not a TTable replacement, but works very much like TSQLQuery. As the name implies, TDISqlite3UniDirQuery is a unidirectional dataset. It does not buffer multiple records in memory. Because of this, you can only navigate using the First and Next methods. There is no built-in editing support: you must run external DELETE, INSERT, or UPDATE SQL statements to manipulate data. Alternatively, you can connect TDISqlite3UniDirQuery to a client dataset using a provider. TDISqlite3UniDirQuery has build-in IProvider support which enables automatic updates with TDataSetProvider / TClientDataset. In addition to that, you can specify special DeleteSql, InsertSql, ModifySql statements for complex queries which TClientDataSet cannot resolve (aggregates, views, for example). Look at the DISQLite3_World demo for a TDataSetProvider / TClientDataSet example. Ralf _______________________________________________ Delphi Inspiration mailing list yunqa@xxxxxxxxxxxxx //www.freelists.org/list/yunqa