Devart Forums

Thanks for contacting us!

Please note, that we've fixed a similar issue regarding "access violation with local master/detail".

The fix will be included in the next build of our product.

You can test this fix with a nightly build.
To obtain a nightly build of SDAC, please specify your license number, IDE version and send us via this contact form: https://www.devart.com/company/contactform.html

Hi,
Thanks for contacting us!

Could you please describe your issue more precisely?
In case if there is any error occurs, please provide us with its full text (you can do it in the form of a screenshot).

Please, create and send us an sample application that demonstrates your issue, with all the necessary files and scripts for creating and fill-in database objects.
You can send all the needed samples via the e-support form: https://www.devart.com/company/contactform.html

Also, please specify which database you are using and its version?

Hi Ron,
Thanks for your request.

Please be informed, that our dbExpress Driver for SQL Server doesn't support connection pooling.

Hi there,
Thanks for your request!

Kindly note that our DAC products currently do not have built-in support for working with JSON in datasets.

You can leave your suggestion regarding JSON support in our DAC products at our user voice forum:
https://devart.uservoice.com/forums/104 ... components

In UniDAC, the ApplyUpdates method is a procedure that writes dataset's pending cached updates to a database and returns no result.
You can find more info about the ApplyUpdates method via the link: https://docs.devart.com/unidac/devart.d ... pdates.htm

Also, kindly note that Devart support team keeps correspondence on the forum in English only.

Hi Olli,
Thanks for contacting us!

The error you mentioned might mean that the application cannot find the appropriate libraries on the computer.

MyDAC uses the following OpenSSL libraries names: first - libcrypto-1_1.dll and libssl-1_1.dll; second - libeay32.dll and ssleay32.dll.

MyDAC will look for the files in directories on your machine, in this order:
- The directory from which your application is loaded.
- The. //System32 system folder.
- The //SysWOW64 folder on a 64-bit system.
- The //Windows folder.
- Current workspace.
- Folders listed in the РАТН environment variable.

Also, this error may indicate a discrepancy between the bitness of the libraries used and the bitness of the application.

In case if you have a 32-bit application, the libraries also needs to be 32-bit, regardless of the MySQL Server bitness.

As a workaround, you can try to place the libeay32.dll and ssleay32.dll files in the directory with the executable file of your application.
Also to solve the issue, you can rename libeay32.dll and ssleay32.dll into libcrypto-1_1.dll and libssl-1_1.dll correspondingly.

Kindly note, that using OpenSSL libraries to create an SSL connection with MySQL server can lead to various issues.

For example, OpenSSL version can be not supported by MySQL server, the bitness of the supplied OpenSSL libraries can differ from the bitness of your application, etc.
To solve the issue, you can use the SecureBridge components.
SecureBridge allows you to establish secure connections within a single application without any external files.

In MyDAC you need to specify the absolute path, including the file name for SSLOptions: CACert\Cert\Key

Hey,
Could you please specify which edition of the IDE do you have?

Please try to do the following steps:
- Remove all our components and all related files with them completely. For this use the "Programs and Features" applet in Windows Control Panel;
- Find all DAC units, like MemUtils.dcu, CRParser.dcu, CLRClasses.dcu, CRTypes.*, MemData.dcu, MemDS.dcu, DBAccess.dcu files on your PC and delete them;
- Find all *dac*.bpl, *dac*.dcp, *dac*.bpi, *dac*.lib, *crcontrols*.bpl, *crcontrols*.dcp, *crcontrols*.bpi, *crcontrols*.lib files on your PC and delete them;
- Install the latest version of UniDAC as Administrator.

After all the steps are done, please check if the issue you indicated has been resolved with the installation of your own component.

Let us know of the results!

Hi Shaun,

We've reproduced the issue and fixed it.

Please note that we have released a new release of dbExpress Driver for SQL Server and have included this fix in it.

Hey,

Please note that in the latest released version of UniDAC 9.3.0 we have improved support for two data types TIMESTAMP WITH TIME ZONE and TIME WITH TIME ZONE.
From this version, fields with type TIMESTAMP WITH TIME ZONE(TIME WITH TIME ZONE) are defined by default as type TDateTimeField(TTimeField).

Kindly note that in UniDAC, when working with data of TIMESTAMP WITH TIME ZONE and TIME WITH TIME ZONE types, the conversion is performed to the local time configured on your computer, and when writing data, the conversion is not performed and the time is entered into the database in the local format configured on the computer.

1) By default, the TIBCConnection.EnableIBCTimeStampTZ property is enabled and fields of type TIMESTAMP WITH TIME ZONE(TIME WITH TIME ZONE) will be represented as type TIBCTimeStampTZField(TIBCTimeTZField).
These types are added directly to work with fields like TIMESTAMP WITH TIME ZONE and TIME WITH TIME ZONE, with which you can extract the necessary information, such as the time zone, write data in the format you need (get or set the value as TSQLTimeStampOffset, etc.) .

2) If the TIBCConnection.EnableIBCTimeStampTZ property is disabled, fields of the TIMESTAMP WITH TIME ZONE(TIME WITH TIME ZONE) type will be represented in the same way as in UniDAC, as a regular TDateTimeField(TTimeField) type, which is limited in functionality compared to the TIBCTimeStampTZField(TIBCTimeTZField) type ).

We'll be adding information about this type to our documentation soon.
Once the documentation is updated we will let you know.

For now, you can update to the latest version of UniDAC and test the added support for the TIMESTAMP WITH TIME ZONE and TIME WITH TIME ZONE data types.

Hi there,
Thanks for your time!

Please be informed, that we have improved support for two data types TIMESTAMP WITH TIME ZONE and TIME WITH TIME ZONE in the latest version of IBDAC 8.2.0

IBDAC implements several options for working with fields of represented types; for this, the TIBCConnection.EnableIBCTimeStampTZ property has been added.

1) By default, the TIBCConnection.EnableIBCTimeStampTZ property is enabled and fields of type TIMESTAMP WITH TIME ZONE(TIME WITH TIME ZONE) will be represented as type TIBCTimeStampTZField(TIBCTimeTZField).
These types are added directly to work with fields like TIMESTAMP WITH TIME ZONE and TIME WITH TIME ZONE, with which you can extract the necessary information, such as the time zone, write data in the format you need (get or set the value as TSQLTimeStampOffset, etc.) .

2) With the TIBCConnection.EnableIBCTimeStampTZ property disabled, fields of the TIMESTAMP WITH TIME ZONE(TIME WITH TIME ZONE) type will be represented as a regular TDateTimeField(TTimeField) type, which is limited in functionality compared to the TIBCTimeStampTZField(TIBCTimeTZField) type.
Please note that when working with data of the TIMESTAMP WITH TIME ZONE and TIME WITH TIME ZONE types, the conversion is performed to the local time configured on your computer, and when writing data, the conversion is not performed and the time is entered into the database in the local format configured on the computer.

We'll be adding information about this type to our documentation soon.
Once the documentation is updated we will let you know.

For now, you can update to the latest version of IBDAC and test the added support for the TIMESTAMP WITH TIME ZONE and TIME WITH TIME ZONE data types.

Hi,

You're always welcome!

Please feel free to contact us if you have any further questions about our products!

Hi,

You're always welcome!

Please feel free to contact us if you have any further questions about our products!

Hi there,
Thanks for your request!

1) We cannot reproduce the behavior you specified based on your description, so please create and send us sample which demonstrates described behavior with all the necessary files and scripts to create and fill-in database objects.
Also, please clarify what database do you use and its version?

2) Regarding the list of event strings, we have reproduced the issue and will investigate its origin.
We will inform you about the results shortly.

Hi,
Thanks for contacting our blog!

Kindly note, that we were unable to reproduce the behavior you specified based on the data you provided.

Could you please compose and send us a sample application reproducing the behavior you have specified with all necessary DDL and DML scripts to create and populate database objects?
You can send all the needed samples via the e-support form: https://www.devart.com/company/contactform.html

Also, please send us the exact list of steps (actions) which leading to the error you indicated.
You can create and send us the screenshot demonstrating the issue.

Additionally, could you please clarify some additional information:
- What version of UniDAC do you have?;
- What version of RadStudio?;
- What version of the database: (FireBird and PostgreSQL);

Hi there,
Thanks for your request!

At the moment a new version of UniDAC 9.3.0 has been released.

Please try to update to the latest version and check if the issue with component registration is resolved.

Let us know the results!

You're always welcome!

We are glad to see that you your issue with "Update or Insert" statements was resolved.

Please feel free to contact us if you have any further questions about our products!