Devart Forums

I cannot reproduce the first problem. Please, send us a complete small test sample to sdac*devart*com that demonstrates the problem.
As to the second problem, we will investigate the possibility to fix it. As soon as we have results, we will let you know.

We have reproduced this problem. We will fix it in the next build of DbxSda. At the moment you should just ignore this exception.

This feature requires SQL Native Client to be installed on client computers. Make sure that it is installed. If does not, download it by this link.

Could you send us a small test example that demonstrates this problem at dbxsda*devart*com? Also include script to create server objects and information about your SQL Server and client versions.

Please, specify the product name and the exact product version you are using to work with database.

The explanation is not clear for me. Please specify what role play dmLookup.tblVendors and dsDetail.DataSet datasets. In what way have you performed the master/detail link? What role plays the VendorUID field in dsDetail.DataSet?

Sorting by click on a column title works automatically only for DAC datasets. For other datasets you should add a handler to the OnTitleClick event of the grid.

Probably the error happens when SDAC tries to establish additional connections to the server (e.g. FetchAll=False mode, NonBlocking=True mode). Try to enable the MultipleActiveResultSets option in TMSConnection. See description of MultipleActiveResultSets in the SDAC help.

You can find an example that demonstrates working with TVirtualTable within SDAC demo projects (SDAC_Inst_Dir\Demos\Win32\SdacDemo\). Open the SdacDemo.dpr, build it and select the VirtualTable item in the tree.
Data from SDAC datasets can be saved to ADO-compatible XML file, and then loaded with ADO components.
There is no way to transfer data directly between recordsets of ADO and SDAC datasets.

The Update checkbox is enabled if there are items in Key Fields and Update Fields listboxes and at least one item is selected in each listbox.

It is unlikely as this is not an asked-for feature and it requires significant changes in code.

DbxSda uses OLE DB to work with SQL Server. Therefore before connecting it is necessary to initialize OLE by calling CoInitialize. In usual applications VCL does it automatically. In console applications, services, additional threads of multithreaded applications it is necessary to call CoInitialize manually. DbxSda cannot execute CoInitialize itself as it may cause unexpected problems at another parts of the program also using OLE.

When you edit the 'virtual' column, TMyQuery tries to post it to the server, but actually this field does not exists in the table. To prevent this you should properly setup SQLInsert, SLQUpdate, and other similar properties. For more information see the MyDAC help, please.

I performed some tests on Windows XP SP3 and found no problems. Please contact me by e-mail at evgeniyd*devart*com, I will send you a small test application. Also specify, on what operations does the problem arise. Does the problem arise on each Windows XP SP3, or there are Windows XP SP3 free from this error?

SDAC has no functionality similar to TClientDataset.CloneCursor.
> Example: to have all prices listed in a tdbgrid and the lowest price in a tdbedit, both editable.
Probably this problem can be solved with using TEdit instead of TDBEdit, or with copying record(s) to TVirtualTable, or in any other way.