I again
After some investigations, I think I found the reason of the problem:
In Windows event log, the string I need is:
Logon Type:<tab><tab><tab>3 (where <tab> is... a tab)The Hex conversion of thei string gives :
4C 6F 67 6F 6E 20 54-79 70 65 3A 09 09 09 33 |Logon Type:...3|
We can see the three tabs as
09 09 09In the Lansweeper database we have the same string, with three tabs, so I made a copy of this string, and pasted it is the query
Where tblNtlogMessage.Message Like '%Logon Type:<tab><tab><tab>3%'
Ok, now it should work ! I save and run the query, and got no result...!
Back to the report, I can see the "Where" doesnt look like it was :
Where tblNtlogMessage.Message Like '%Logon Type: 3%'
And an Hex conversion confirms:
4C 6F 67 6F 6E 20 54 79-70 65 3A 20 20 20 33 |Logon Type: 3|
The original
<tab><tab><tab> has been changed to
<spc><spc><spc> (space)!!!
So it seems that the Query builder of Lansweeper cannot understand <tab>, and replaces it by a <spc> (space)
By the other hand, if I use the same filter, with tabs, in the result window of the reports, it works !
At last, if I use a wildcard (%) in my query, (Where tblNtlogMessage.Message Like '%Logon Type:%3%') it doesn't work either...
Ok, as I said, I think I got the reason, but not the solution
Any clue ?
Thanks all
Best regards
Flo