mvanrijnen

FIrst, which email components ? Which failures ? Which false negatives (if this is virusscan/spam detection, has nothing todo with indy itself, but how you use indy) Maybe your having troubles with the latest development of microsoft, they are pulling out old TLS versions. see: Preparing for TLS 1.2 in Office 365 and Office 365 GCC - Microsoft 365 Compliance | Microsoft Docs (just as info not a solution) you have any logging of the failures?

no answer but just for to be clear, your talking about this: Per Monitor V2 - RAD Studio (embarcadero.com) ?

strange, delphi is not drawing these forms itself? vcl is just a door to the underlaying windows api? or does this depends wether you'r using vcl styles or something similar?

Yes, but not with Crosstalk, i just made an Com library in VS Community, just imported the tlb into Delphi and it works. I did not know that EWS was that old, have to take a look into it. I see we're supposed to work with Overview of Microsoft Graph - Microsoft Graph | Microsoft Docs instead. For now it works for us with the EWS. (i do that for more thing this way, because there's so much more available in .net these days) I'm sure going to take a look at AtoZed CrossTalk, never heard/read of it 🙂

Here the same, only for O365 i have build a "proxy" in C#, we use EWS for that now. (Exchange Web Services (EWS) Managed API reference | Microsoft Docs)

Can't you be a little more specific which problems you'r having with Indy ?

main problem is that we have now a buggy D11, but they don't look back and fix the D10 version, there a lot of bugs that they could fix, but they just don't. i thought part of the subscription program was that they would fix bugs from a previous release. They entered a path where they never gonna get a (reasonable) bug fixed product. very very disappointed.

yes, you'r right, i think it's because this: i got cought up in that. So what i can see is that intenral in his code he's storing the dates as strings, got a little bit mixed up with the DB, easy, easy, easy, take a breath.

Okay, so you DB is ok, it's a DateTime field (or timestamp field), then the main problem is probably the storage in the tree, is this a visual treeview thing? best is to take a look at that, if you can improve the storage of the datetime value with the tree item, and keep a record or a pointer to a class instance with the correct data, so you can use your file datetime as a real datetime, then you won't have the problems with the strtodatetime thing when quering the database. it's only a tip, or let's say positive critisism 😉

then use the function DateTimeToStr and StrToDateTime with the format options, already mentioned before. i would be sure then, to keep a fixed format in the database if it has to be a string like YYYYMMNNHHNNSS, or use ISO8601 to store and retrieve. but keep the points of conversion as minimum as possible, there will be a point where it's gonna bite you, been there, done that 🙂 But at the end, it's something you have to figure out yourself. I would go back and take a look if you can change the >>> DateTimeToStr(FileInfo.TimeStamp)); >>> this to tree > to DB to FileInfo.TimeStamp----->Database ------>Visualize DateTimeToStr()

Why keep converting a Date(Time) to a string, keep it a a date and let FireDac worry about the conversion to the correct db format. (as said before, keep away from datetime to string conversion (or viceversa) with something like this) What code you now have, the whole SQL statement and the assignment of parameter values?

take a look at: System.SysUtils.FileDateToDateTime - RAD Studio API Documentation (embarcadero.com) (assuming you get the filedatetime with a standard delphi function).

just for the example: var myDate : TDate; begin myDate := EncodeDate(2021, 10, 3); .... // Make sure that myDate only contains the Date part, even when you declare a var as TDate it still can contain a time part !! // so thats why i make sure in the assignment, it depends on you own code if you need the DateOf() here. FDQuery2.Params.ParamByName('MyDateFrom').AsDate := DateOf(myDate); FDQuery2.Params.ParamByName('MyDateTill').AsDate := IncDay(DateOf(myDate)); ..... end;

haha, the StrToDate shit, is just taken from the topicstart, ofcourse in realworld we do not use this in realcode.

FDQuery2.SQL.Add('Select * from Projects'); FDQuery2.SQL.Add('WHERE MyDateTime>=:MyDateFrom'); FDQuery2.SQL.Add(' AND MyDateTime<:MyDateTill'); FDQuery2.SQL.Add('ORDER BY MyDateTime'); FDQuery2.Params.ParamByName('MyDateFrom').AsDate := StrToDate('03/10/2021')); FDQuery2.Params.ParamByName('MyDateTill').AsDate := IncDay(StrToDate('03/10/2021')); FDQuery2.Open; please keep forum in english.

or use COALESCE In interbase we don't have ISNULL(MyInt, 0) function, but we do have COALESCE which seems to do the same thing ?

Did you change "HKEY_CURRENT_USER\Software\Embarcadero\BDS\21.0\LSP" to "HKEY_CURRENT_USER\Software\Embarcadero\BDS\22.0\LSP" ?

I have a helper for this kind of stuff (in real the helper contains some more methods : ) : TMyFieldHelper = class helper for TField public function AsIntegerDef(const ADefault : integer) : integer; end; function TMyFieldHelper.AsIntegerDef(const ADefault: integer): integer; begin Result := ADefault; try if (not Self.IsNull) then Result := Self.AsInteger; except {TODO -oOwner -cGeneral : check which to swallow ... } // swallow any exception end; end;

Look impressive ! Especially the zooming looks good.

i already could click them? Ah, see it now 😉 Good tip!

ah full 4k support, time to ask the boss for new monitors 🙂

Installed it on notebook running Windows 11 Beta. Plain installation went ok, no exception orso, simple test projects are running ok. tomorrow test the codecompletion somewhat more.

Database DDL's

see also: delphi - XE4: How to change exe output name base on platform? - Stack Overflow

Yes i have had the same, with invoice recognition software i wrote. And then you have the suppliers where the financial formats differ from the "data/content" format. So we had a base setting for the numeric formats per application, per supplier (inherited), per content fields/table (inherited).