pcsoft.us.windevCopyright 2026, PC SOFT9 Mar 2018 16:47:51 Z9 Mar 2018 16:47:51 ZHello everybody, I've discovered two curiosities while working with an WinDev application on two different client systems, that I would like to discuss with you. Both clients connect to the same database, using the same compiled exe and the same source code. I'm using the native access for SQL-Server. My setup: Database: Microsoft SQL Server 2014, Client 1: Windows 7 Client 2: Windows Server 2012 R2 Issue 1: Dates are retrieved different from the database. They are stored as datetime2. While accessing the date field from a query: client 1 receives: 20130902140928970 client 2 receives: 20130009020104009 I already checked the region date settings for both environments, they are both set to german time format. For me this seems weird. Any suggestions what might cause this issue? Issue 2: While generating the exe-file within Framework (2/2) I have three library files, that I cannot uncheck. Native SQL Driver wd210sqlserver.dll First use Native SQL Driver wd210sqlserver2.dll First use Native SQL Driver wd210sqs.dll First use When I launch the application it only works when I delete "wd210sqs.dll". Otherwise I get an error that ntwdblib.dll is missing. Any suggestions how I can exclude this dll? I'm curious for your thoughts. Thanks in advance for any help.30WEBDEVen_UShttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/64878-handling-dates-different-envrionments/read.awpmoderateur@pcsoft.fr (El moderador)webmaster@pcsoft.fr (El webmaster)