AV in midas.dll

[radub]

Hello,

ODAC latest versions, client/server Delphi XE5
We have the following situation:
The client is compiled on 32b platform and the server on 64b platform.
The client contains a TClientDataset and a TDCOMConnection.
The server contains a TOraSession, a TDatasetProvider and a TOraTable. The underlying table has a few fields (doesn't matter how many and what datatype), one of them is varchar2 or integer with a default value (no matter the value). Also the DefaultValues flag from TOraTable's Opions is set to true - very important.
After establishing the connection, trying to put the clientdataset in Insert mode generates an AV in midas.dll.
If none of the table's fields have default value, or the DefaultValues flag is set to false, the AV doesn't occur.
The AV doesn't occur either, if the server is compiled on 32b platform.

I've already built a demo for you; just give me an email address.
Any idea how to circumvent this situation?

[AlexP]

You can send the sample to alexp*devart*com .

[radub]

Hello,

I've sent the sample in the same day.. Have you recevied it? Did you manage to reproduce the problem?

Thank you,
Radu B.

[AlexP]

Unfortunately, we haven't received your letter, please send it once more support*devart*local

[radub]

I have re-sent the original mail at [email protected], not at [email protected].
Please send a confirmation letter to let me know that you have received the mail and managed to reproduce the problem.

Radu B.

[radub]

Have you got the mail?

[AlexP]

We have received your email and will investigate the problem . We will try to answer shortly.

[radub]

Hello,

No news?

[AlexP]

We continue the problem investigation, and as soon as we have any results, we will inform you.

[radub]

Hello,

It has been more than a month waiting for a shortly response, and I have no solution for the clients.
What is going on with the issue?

Thank you,
Radu B.

[AlexP]

We have investigated this problem in more details and found out that AV occurs in DataSnap, not in our components. If you set default field values in FireDAC, then this will lead to similar AV. The same problem occurs even when using ClientDataset without working with a DB. We have reported this issue to embarcadero quality central: https://quality.embarcadero.com/browse/RSP-9888

[radub]

I see.
But I don't understand why this happens only in ODAC implementation, the SDAC works perfectly.

[AlexP]

Since this error occurs not in our products, we can't investigate the cause of its occurrence more deeply.