John, I'm reluctant to share this only because I was never really sure it was effective, but here goes:
I had the same sorts of issues with the SQL Toolkit from NI (version 3). Since date/time values out of the DB are necessarily converted to string along the way, you're at the mercy of the user's regional settings. My attempt at fixing the perceived problem involved creating a couple of Vis which wrapped WinAPI calls 'SetLocaleInfo' and 'GetLocaleInfo'. I was never really convinced that they had the desired effect - IIRC, the API calls change the date and time 'picture' for the calling thread, and I'm not certain that you can guarantee that the SQL conversion code runs in the same thread. But I'll bundle them up and mail them to you (last saved in 6.02) if you'd like. My more recent work uses the DB Connectivity Toolset, which handles date/times as OLE Variants and comes with its own set of gotchas. Best regards, Dave David J Boyd Senior Test Engineer Respironics 175 Chastain Meadows Court Kennesaw GA 30144-3724 (V) 770-429-2809 (F) 770-423-2300 ======================================================================== CONFIDENTIALITY NOTICE ---------------------- This message, together with any attachments, may be legally privileged and is confidential information intended only for the use of the individual or entity to which it is addressed. It is exempt from disclosure under applicable law including court orders. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender and delete this message, along with any attachments, from your computer.
