-
Juan Alberto Lopez de las Heras
- PowerServer
- Monday, 27 April 2026 03:21 PM UTC
Hello
We are currently working on a migration project from PowerBuilder 2019 + PowerServer 2020 to PowerBuilder 2022 + PowerServer 2022, and we would like to request your technical assistance regarding a date-related issue we are facing during testing.
Project context
We currently have several applications developed in PowerBuilder 2019 and deployed using PowerServer 2020. In that environment, the applications work correctly.
We have started the migration to PowerBuilder 2022 and PowerServer 2022, and we have already managed to:
compile the application successfully in PB 2022,
deploy it to PowerServer 2022,
run it correctly on the new server,
solve initial issues related to Web API URL configuration and client/Web API version synchronization.
However, we are now facing a specific problem related to date handling.
Issue found
In client/server mode, the application works correctly.
In PowerServer 2022, when executing certain operations against SQL Server, we get date conversion errors such as:
“The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.”
We have identified two different scenarios:
1. Embedded SQL / direct INSERT
We have an INSERT similar to this:
INSERT INTO table_name
( user, fech_conexion, computername )
VALUES
( :id_aplicacion.user,
:id_aplicacion.fech_conexion,
:id_aplicacion.computerName)
USING SQLCA;
The variable id_aplicacion.fech_conexionis defined as datetime.
With DisableBind=1, we were getting the varchar -> datetime conversion error.
After changing to DisableBind=0, the problem seems to be solved for direct embedded SQL statements.
2. SQL generated/exported from DataWindow
The problem still remains in SQL generated/exported by DataWindow.
At first, the exported SQL produced ambiguous date literals such as:
fecha >= '24/04/2026 00:00:00'
After adjusting the configuration, it now generates something like:
and ('' fecha >= '2026-04-22')
This causes a syntax error near the field name.
If we manually remove the extra leading quotes and keep the correct date format, the statement works correctly.
What we have already tried
Changing DisableBind=1 to DisableBind=0
Testing DateFormat and DateTimeFormat in DBParm
Trying SET DATEFORMAT, although that approach has not been stable for us
Reviewing the exported SQL and confirming that the issue seems related to how PowerServer / DataWindow generates or transforms date literals
Our questions
We would like to confirm with you:
What is the correct and recommended way to configure date and datetime handling in PowerServer 2022 with SQL Server during a migration from PB 2019 / PowerServer 2020.
Whether there are any specific recommended settings for:
DisableBind
DateFormat
DateTimeFormat
ProviderString
SQL Server session language / date format
Whether this behavior in DataWindow-generated SQL is a known behavior or possibly a defect.
What would be the best way to prevent invalid date formats or extra quotes from being generated when the application runs in PowerServer 2022.
We would greatly appreciate any guidance, official recommendation, or sample configuration you can provide.
Thank you very much for your assistance.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.