I'm using German regional settings. Creating a creteria like "datetimefield is greater or equal to 24.11.2016 00:00" is working very well. But if I want to select a given value from database all values are shown in wrong format e.g. "08/30/2016 02:01:17". Any idea how to solve this issue.
Hi Sergey,
sorry to say but the fix does not solve the problem completely. Please see my screenshots below:
Hope you can help.
Cheers - Mark
Hello, Mark.
The fixed version is available for downloading. Sorry for keep you waiting for so long.
Hello, Mark.
Sorry for keep you waiting for so long.
The fixed build will be available on Monday.
Hi Sergey,
could you provide a release date for the fix, please? Last version I can see in the download area is from the 22th of December and some days younger than your last post.
It's quit important for me to sort out this problem in our solution.
Thanks - Mark
Hello, Mark.
Sorry for keep you waiting for so long.
The bug with incorrect datetime format is fixed. The fix will be included in the next build that will be available till the end of this week.
Hello, Mark.
Thank you for your feedback.
We will investigate this problem and let you know about results shortly.
Hi Sergey,
thanks for your answer but I'm talking about your criteria builder component I have some trouble with. I have added a picture to explain my problem. Hopefully this might help to give me the missing hint.
The criteria is formatted like expected in German notation but the list of all possible value isn't. Any idea how to sort out this? You also can see the datagridview with its first two rows and again this is well formatted, too.
Cheers - Mark
Are you talking about Active Query Builder or about FlySpeed SQL Query?
If it's really about Active Query Builder, please note that it doesn't have any means to display the result data. Chances are that you use the standard data grid or a third-party data browsing control. You should refer to the documentation for this control to learn how to change the data formatting settings.
Hello, Mark.
Thank you for your bug report. The bug is fixed in the latest version.