Hey,
Thanks for your request!
Unfortunately, the data you provided is not enough to reproduce the issue.
Please clarify which version of PostgreSQL do you use?
Also, please send us a small sample that uses UniDAC and demonstrates incorrect behavior, as well as DDL scripts to create and fill-in database objects.
You can submit it via the form on our website: https://devart.com/company/contactform.html
Search found 103 matches
- Tue 27 Sep 2022 10:23
- Forum: PostgreSQL Data Access Components
- Topic: Column pd.adsrc does not exist
- Replies: 1
- Views: 41523
- Wed 21 Sep 2022 09:27
- Forum: dbExpress driver for PostgreSQL
- Topic: dbExpress driver 3.8.12 for PostgreSQL - Assertion failure (D:\Projects\Delphi\Dac\PostgreSql\Source\PgSQLProtocol.pas)
- Replies: 5
- Views: 10208
Re: dbExpress driver 3.8.12 for PostgreSQL - Assertion failure (D:\Projects\Delphi\Dac\PostgreSql\Source\PgSQLProtocol.p
Thank you for choosing our products! Do not hesitate to ask if you have any other questions. Have a nice day.
- Fri 16 Sep 2022 13:43
- Forum: Universal Data Access Components
- Topic: Random Error with PostgreSQL
- Replies: 3
- Views: 7804
Re: Random Error with PostgreSQL
Hi Christian,
"An existing connection was forcibly closed by the remote host" means that the server closed the connection.
The reason could be:
1) Sending incorrect data to the server
2) Network problems
3) All system resources have been used
4) Application error
Please note, that without a sample that reproduces the issue we cannot name its cause.
"An existing connection was forcibly closed by the remote host" means that the server closed the connection.
The reason could be:
1) Sending incorrect data to the server
2) Network problems
3) All system resources have been used
4) Application error
Please note, that without a sample that reproduces the issue we cannot name its cause.
- Wed 14 Sep 2022 11:23
- Forum: Universal Data Access Components
- Topic: Random Error with PostgreSQL
- Replies: 3
- Views: 7804
Re: Random Error with PostgreSQL
Hi Christian,
Thanks for contacting us!
Could you please update to the latest UniDAC 9.3.0 and see if the issue is reproduced?
You can download the latest version from our website via the following link: https://www.devart.com/unidac/download.html
In case if the issue will be reproducing, kindly create and send us sample which demonstrates described behavior and DDL scripts to create and fill-in database objects.
You can send a sample using the form on our website: https://devart.com/company/contactform.html
Thanks for contacting us!
Could you please update to the latest UniDAC 9.3.0 and see if the issue is reproduced?
You can download the latest version from our website via the following link: https://www.devart.com/unidac/download.html
In case if the issue will be reproducing, kindly create and send us sample which demonstrates described behavior and DDL scripts to create and fill-in database objects.
You can send a sample using the form on our website: https://devart.com/company/contactform.html
- Thu 08 Sep 2022 13:48
- Forum: ODBC Drivers
- Topic: ODBC: ERROR [HY000] [Devart][ODBC][PostgreSQL]Trial period is expired"
- Replies: 1
- Views: 8833
Re: ODBC: ERROR [HY000] [Devart][ODBC][PostgreSQL]Trial period is expired"
Hi Jorge,
Thanks for contacting Devart!
Please try to do the following steps:
-Close all applications or services using our driver and uninstall it;
-During the uninstaller program, select the option to remove driver activation information;
-Make sure the driver was successfully uninstalled. For this go to the folder with the previously installed driver and check that it is empty. Delete this folder if it exists and restart your computer;
-Run the driver installer as administrator;
-Activate the driver during the installer - this step is very important;
Please let us know the results!
Thanks for contacting Devart!
Please try to do the following steps:
-Close all applications or services using our driver and uninstall it;
-During the uninstaller program, select the option to remove driver activation information;
-Make sure the driver was successfully uninstalled. For this go to the folder with the previously installed driver and check that it is empty. Delete this folder if it exists and restart your computer;
-Run the driver installer as administrator;
-Activate the driver during the installer - this step is very important;
Please let us know the results!
- Tue 23 Aug 2022 05:21
- Forum: Universal Data Access Components
- Topic: Upgrade 8.3.2 >> 8.4.1
- Replies: 12
- Views: 12025
Re: Upgrade 8.3.2 >> 8.4.1
Hi,
Thanks for contacting us!
Kindly note, that currently available version is 9.2, which you can download via the following link: https://www.devart.com/unidac/download.html
Thanks for contacting us!
Kindly note, that currently available version is 9.2, which you can download via the following link: https://www.devart.com/unidac/download.html
- Tue 23 Aug 2022 05:21
- Forum: PostgreSQL Data Access Components
- Topic: PgQuery Type mismatch for field.. expecting: WideMemo actual: Float.
- Replies: 9
- Views: 19473
Re: PgQuery Type mismatch for field.. expecting: WideMemo actual: Float.
Hey,
Thanks for your request.
Please be informed, that unfortunately we were unable to reproduce the described behavior and did not receive a test case.
Kindly specify the exact steps to get the misbehavior and submit a sample application that demonstrates the misbehavior along with DDL scripts to create and fill-in database objects.
Submit them via the form on our website: https://devart.com/company/contactform.html
Kindly note that sooner you will provide us with an example, the sooner we can start to investigate your issue.
Thanks for your request.
Please be informed, that unfortunately we were unable to reproduce the described behavior and did not receive a test case.
Kindly specify the exact steps to get the misbehavior and submit a sample application that demonstrates the misbehavior along with DDL scripts to create and fill-in database objects.
Submit them via the form on our website: https://devart.com/company/contactform.html
Kindly note that sooner you will provide us with an example, the sooner we can start to investigate your issue.
- Wed 17 Aug 2022 09:52
- Forum: Universal Data Access Components
- Topic: Prepared Statements (PostgreSQL)
- Replies: 5
- Views: 8692
Re: Prepared Statements (PostgreSQL)
Thanks for using our product!
Please let us know is any kind assistance from our is required. We always happy to help!
Please let us know is any kind assistance from our is required. We always happy to help!
- Wed 17 Aug 2022 09:52
- Forum: PostgreSQL Data Access Components
- Topic: PgQuery Type mismatch for field.. expecting: WideMemo actual: Float.
- Replies: 9
- Views: 19473
Re: PgQuery Type mismatch for field.. expecting: WideMemo actual: Float.
Thanks for using our product!
Please let us know is any kind assistance from our is required. We always happy to help!
Please let us know is any kind assistance from our is required. We always happy to help!
- Thu 04 Aug 2022 10:54
- Forum: Universal Data Access Components
- Topic: UniDAC Component for FastReport FMX 64 bits.
- Replies: 19
- Views: 8461
Re: UniDAC Component for FastReport FMX 64 bits.
Please be informed, that the example for Fast Report FMX works for both x86 and x64 bit FMX applications.
The example demonstrates the main functionality for working with components, and not all of their capabilities.
In case if you still have questions after studying the example, please feel free to contact us any time.
The example demonstrates the main functionality for working with components, and not all of their capabilities.
In case if you still have questions after studying the example, please feel free to contact us any time.
- Tue 02 Aug 2022 12:37
- Forum: Universal Data Access Components
- Topic: UniDAC Component for FastReport FMX 64 bits.
- Replies: 19
- Views: 8461
Re: UniDAC Component for FastReport FMX 64 bits.
After installing UniDAC using the link provided in the previous answer, the demo projects will be installed in the folder.
"c:\Users\%UserName%\Documents\Devart\UniDAC for %IDEVersion%\Demos\
where %UserName% is the user name for which UniDAC is installed,
%IDEVersion% - IDE version for which UniDAC is installed
Among these projects, you can also find an example of how UniDAC works with Fast Report FMX, as well as installation packages for the necessary components.
You can see the components you are interested in the folder
"c:\Users\%UserName%\Documents\Devart\UniDAC for %IDEVersion%\Demos\ThirdParty\FastReport\FMX"
where %UserName% is the user name for which UniDAC is installed,
%IDEVersion% - IDE version for which UniDAC is installed
"c:\Users\%UserName%\Documents\Devart\UniDAC for %IDEVersion%\Demos\
where %UserName% is the user name for which UniDAC is installed,
%IDEVersion% - IDE version for which UniDAC is installed
Among these projects, you can also find an example of how UniDAC works with Fast Report FMX, as well as installation packages for the necessary components.
You can see the components you are interested in the folder
"c:\Users\%UserName%\Documents\Devart\UniDAC for %IDEVersion%\Demos\ThirdParty\FastReport\FMX"
where %UserName% is the user name for which UniDAC is installed,
%IDEVersion% - IDE version for which UniDAC is installed
- Mon 01 Aug 2022 09:46
- Forum: Universal Data Access Components
- Topic: UniDAC Component for FastReport FMX 64 bits.
- Replies: 19
- Views: 8461
Re: UniDAC Component for FastReport FMX 64 bits.
Hi there,
Thanks for your request!
Please note, that the components for working with Fast Report FMX x86/x64 are available in UniDAC starting from version 9.0.1.
You can download them from the link below:
https://www.devart.com/unidac/download.html
Thanks for your request!
Please note, that the components for working with Fast Report FMX x86/x64 are available in UniDAC starting from version 9.0.1.
You can download them from the link below:
https://www.devart.com/unidac/download.html
- Mon 01 Aug 2022 09:43
- Forum: PostgreSQL Data Access Components
- Topic: Manage pooling connection
- Replies: 1
- Views: 7426
Re: Manage pooling connection
Hi Antonello,
Thanks for contacting us!
Yes, you have set all parameters correctly.
You can find more information about the connection pool using the links:
https://docs.devart.com/pgdac/work_pooling.htm
https://docs.devart.com/pgdac/devart.da ... ooling.htm
An example of using the connection pool you can find in our demo:
"c:\Users\%UserName%\Documents\Devart\PgDAC for %IDEVersion%\Demos\Miscellaneous\FailOver"
where %UserName% is the username for which PgDAC is installed,
%IDEVersion% - IDE version for which PgDAC is installed
Thanks for contacting us!
Yes, you have set all parameters correctly.
You can find more information about the connection pool using the links:
https://docs.devart.com/pgdac/work_pooling.htm
https://docs.devart.com/pgdac/devart.da ... ooling.htm
An example of using the connection pool you can find in our demo:
"c:\Users\%UserName%\Documents\Devart\PgDAC for %IDEVersion%\Demos\Miscellaneous\FailOver"
where %UserName% is the username for which PgDAC is installed,
%IDEVersion% - IDE version for which PgDAC is installed
- Wed 27 Jul 2022 11:38
- Forum: PostgreSQL Data Access Components
- Topic: PgQuery Type mismatch for field.. expecting: WideMemo actual: Float.
- Replies: 9
- Views: 19473
Re: PgQuery Type mismatch for field.. expecting: WideMemo actual: Float.
Hi Stewart,
Thanks for using our product!
We are always happy to help.
Thanks for using our product!
We are always happy to help.
- Mon 20 Jun 2022 11:49
- Forum: PostgreSQL Data Access Components
- Topic: working with large objects
- Replies: 1
- Views: 8429
Re: working with large objects
Hi Wolfgang,
Thanks for your request!
The TPgLargeObject class is not designed to work with the type bytea, but rather to work with the type PostgreSQL large objects.
The bytea type is not equivalent to PostgreSQL large object.
With the bytea type you can work as with TBlobField.
You can find more information about the TPgLargeObject class at the following link:
https://docs.devart.com/pgdac/devart.pg ... object.htm
You can find more info about PostgreSQL large objects at the following link:
https://www.postgresql.org/docs/14/largeobjects.html
An example of how the TPgLargeObject class works with PostgreSQL large objects can be found at the link:
https://docs.devart.com/pgdac/work_large_objects.htm
More info about the bytea type you can find at the provided link:
https://www.postgresql.org/docs/current ... inary.html
Could you please clarify the 404 error appeared when using the https://www.devart.com/company/contactform.html contact form?
Regards,
Evgeniy
Thanks for your request!
The TPgLargeObject class is not designed to work with the type bytea, but rather to work with the type PostgreSQL large objects.
The bytea type is not equivalent to PostgreSQL large object.
With the bytea type you can work as with TBlobField.
You can find more information about the TPgLargeObject class at the following link:
https://docs.devart.com/pgdac/devart.pg ... object.htm
You can find more info about PostgreSQL large objects at the following link:
https://www.postgresql.org/docs/14/largeobjects.html
An example of how the TPgLargeObject class works with PostgreSQL large objects can be found at the link:
https://docs.devart.com/pgdac/work_large_objects.htm
More info about the bytea type you can find at the provided link:
https://www.postgresql.org/docs/current ... inary.html
Could you please clarify the 404 error appeared when using the https://www.devart.com/company/contactform.html contact form?
Regards,
Evgeniy