Devart Forums

pharry wrote:Is there a way to make dbexpress use OLE DB rather than the native client?

This possibility was added in DbxSda 4.25.7. You can setup which provider to use through the VendorLib property of TSQLConnection. For more information see the Readme.html file. You will find it in the DbxSda installation directory.

Please take a look at this article. if it will not help to cope with the problem, send your registration information to sdac*devart*com. We will send you a test version of the driver.

Please answer some questions about the problem:
Are you using transactions, locking, or CachedUpdates mode in your application?
Does the problem appear for update/insert operations, or only for delete?
Is the problem reproduced with some of UniDAC demos?

Also supply the following information:
- the exact version of UniDAC. You can see it in the About sheet of TUniConnection Editor;
- the exact version of your IDE;
- the exact version of SQL server and client. You can see it in the Info sheet of TUniConnection Editor.

I cannot reproduce this problem. Could you send us the database created with the previous version of the driver and a test application that reproduces this problem? Also specify the exact version of your IDE.

VirtualTable does not support aggregate fields.
What do you mean under 'groupstates'?

SDAC includes the Performance demo. It is intended to test the performance of SDAC. Unfortunately, there is no other similar demos in SDAC.

It is a designed behavior of TVirtualTable.

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

Please check connection settings, antiviruses, firewalls, etc.
If this does not help, specify the exact error message text.

Thank you for information. We have reproduced the problem. The investigation is in progress. As soon as we get more information about the problem we will let you know.

>May be use of IDENT_CURRENT(UpdatingTable) - is better decision?
I think that you should decide by yourself whether of these statements to use.

>@@identity can return identity from another table?
Yes, it can.

> Can I get this script in run-time and append
There is no simple way to do this. You should write this statement at design time.

You should do the following:

1. Place this code in the BeforeUpdateExecute event of your stored procedure 2. Replace this line in SQLInsert: with this one: For more information about difference between SCOPE_IDENTITY() and @@IDENTITY you can read in this topic of MSDN.

I could not reproduce the problem. Try to check the latest build of SDAC (4.50.0.35). If it does not help, send me the dump file by e-mail at sdac*crlab*com. Also specify the exact version of your client. You can see it in the Info sheet of TMSConnection Editor.

I can suggest running queries withing a transaction with the appropriate isolation level (e.g. ilIsolated). For more information about isolation levels see the TCustomMSConnection.IsolationLevel topic in SDAC help.

Depending on connection settings you may need to install SQL OLE DB provider, SQL Native Client provider, or SQL Server Compact edition version 3.1 or 3.5.
Please specify the server version you are working with, class of your connection (TMSConnection/TMSCompactConnection), and values of the Provider/CompactVersion option.