Devart Forums

Thank you for information.
We have reproduced the problem and fixed it.
This fix will be included in the next build of MyDAC 5.

Preparing the query also takes some time on the server if you use the standard driver.
There is no way to get the fields description without executing or preparing the query.
We sure that executing the query without fetching the data to get its fields description is much better way rather than preparing it.
We will try to make some performance optimization but it can't be significant.

Most likely the new build of SDAC 4 won't be available within next week.

We have found a performance issue of calculated and lookup fields and fixed it.
This fix will be available in the next build of SDAC 4.

Thank you for information.
We have reproduced the problem and fixed it.
This fix will be included in the next build of DbxSda.
Please watch for announcements at the forum.

You can also specify unit output directory to another folder.
Use the "Project->Options->Directories/Conditionals->Unit output directory" editor for this.

We couldn't reproduce the problem.
Please make sure that you use valid installation packages for Delphi 7 and Delphi 2007.
Use the sdac410d7xxx.exe file to install SDAC for Delphi 7 and the sdac410d11xxx.exe file to install SDAC for Delphi 2007.

It seems that this folder is read-only.
Try to uncheck the Read-only property in the folder properties window.

You should specify the ParamType and DataType for all parameters in the query only if you use the Prepare method. That is why it works in design time. Do not use the Prepare method if you can.

DbxSda has no such restriction. Error message is defined in a unit from Borland. We think Borland uses it for commercial purposes. Try to delete the default.bpr file in the borland\bin folder. Backup it previously.

SQL Server doesn't support overlapped transactions.
Nested transactions are not supported by OLE DB providers for SQL Server.
So you can use only a single transaction at a time using DbxSda.

This is a dbExpress bug with parsing parameters in queries.
Modify your query, or use parameters instead.

Thank you for your sample. It did help us very much.
We have reproduced the problem and fixed it.
This fix will be included in the next build of SDAC 4.

If you are registred user of DbxSda, please send us (evgeniym*crlab*com) your licence number.
If you use DbxSda Trial edition, please send us the e-mail address you want to recieve DbxSda for further testing.

Please set the TMSConnection.Options.AutoTranslate property to False and try again.
In such case SQL Native Client does not use Unicode to convert data transferred between the client side and CHAR, VARCHAR, or TEXT columns, variables, or parameters in a SQL Server database. Please see MSDN and the SDAC help for more information about this property.