08-19-2020 11:43 AM - edited 08-19-2020 11:44 AM
@MarkTTHSAS wrote:
Some great suggestions here! I like the possibility that the time is being reported incorrectly based on the user - that had never previously crossed my mind! - but it is the most obvious explanation.
If it looks like a duck...
...it could very well be a decoy. 😉
Side note:
I always thought duck decoys looked so fake... until I saw one next to a real duck and the real duck looked just as fake!
08-26-2020 09:40 AM
I looked at the date formats for the two users and as far as I can see they are identical... This was in Control panel --> Clock and region --> Change Date time or number formats. Is there another location which could impact the format?
I looked at the DSN settings to see if the format reported back from SQL Server could be different, but nothing jumps out. Is there a setting here which would impact how the date is returned?
08-26-2020 09:56 AM
@RavensFan wrote:
You should add some code to debug. Put a separate indicator in like an array of booleans that show the results of the decision logic as to whether the background should be pink or not. This will help you to determine if it is a logic error or a graphic error in LabVIEW.
Have you done this? Seems like a solid next step. Maybe also put an indicator for the system time you are comparing all the other times to.
Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.
10-19-2020 07:25 AM
Finally got to this!
The date format turns out to be the issue. Even though it was being displayed in my multicolumn listbox in the correct format (YYY-mm-dd) it was coming back from SQL server in the default format of the user (mm/dd/yy) and hence my logic was not working.
Thanks for all the help!