datasets. Therefore you no longer need TClientDataSet and TDataSetProvider to display and modify data implementing update logic - A multi-table join, stored procedure and union results can be easily edited with TDBXUpdateSQL linked to any eXtension dataset while the standard dbExpress usage requires writing the code Improve your software scalability - of the application server or web application with the built-in connection pooling multi-database

multitalbe, updateobject, tclientdataset, native, bidirectional, dbaware, alternative, db aware, custo, multidatabase, migration, data, join

datasets like other database handling products. Firstly it doesn`t concentrate maintenance of datasets, but offer up users lot of built functions never a product before. Shortly it`s proud of the most important functions: - Data manipulation between two datasets: Help user to import & export datas with macros and functions (merge datas). - Compare two dataset by user specified unique fields. - Multiple SQL Editors Script Executing (SQL Manager):

search, merge data, sql manager, database desktop, export, data comparison, edit

SMExport is a component suite for data export from TDBGrid/TDataSet (with BDE or without) into: - XLS (Excel spreadsheet without OLE) - MS Excel - MS Word - MS Access (DAO/MS Jet) - Text (fixed or CSV) - HTML - XML - Lotus 1-2-3 - QuattroPro - RTF (Rich Text format) - SYLK (Symbolic Link) - DIF (Data Interchange Format) - SQL-script - Paradox/DBase files - MS Windows clipboard - other dataset component.

sylk, dump, fixed, paradox, spreadsheet, html, text, dbase, export, tdbgrid, quattro, grid, dbgrid

Generated code can access databases with TIBStoredProc TIBQuery TIBClientDataSet from the IBX palette, thus significantly reducing programmer`s job on writing the standard code for stored procedures handling. Works with action procedures (those having no input/output), as well as procedures having input/output parameters and procedures returning datasets.

tibclientdataset, stored procedure, tibquery, tibstoredproc, interbase, delphi

SMLogging components for errors/exceptions debug, tracing of messages, events - useful processing of errors and exceptions, send the bug reports with screenshot - control center: message processing, hints, help, idle, (de)activation, minimization/maximization, active control change, form change, changing any windows settings - trace the dataset: scroll, state change, value edit - trace the file/directory/drive change - NT events reader

attachment, smlogging delphi component, dataset, raise, event, state, email, trace, nteventlog, exception, error, screenshot

DataSet class: the control always has to be bound to a dataset or other source for its data. Others consider that the DataSet class is too slanted towards working with XML documents. The SourceGrid control allows simple data to be displayed, without relying on XML to do it. However, while the SourceGrid control is potentially useful for simple applications, it lacks more advanced features offered by other grid controls. For example, SourceGrid lacks

winform grid, grid vb net, grid component, grid dotnet, grid library, grid dll, grid net, grid bound, grid control, grid unbound