Weird behavior moving from OLEDB to Windev Native Access on SQL Server 2008

Re: Weird behavior moving from OLEDB to Windev Native Access on SQL Server 2008:SOLVED

guest — 10 Jun 2015 18:40:00 Z

I've solved my issue. Apparently somewhere deep in the bowels of my projects analysis Windev though one of my tables (pretty muc…

guest — 8 Jun 2015 13:17:00 Z

Steve Why don't you try to use v29 native Sql on wd19 as your native wd20 drivers come with all<= v20 and if it works, it's t…

guest — 4 Jun 2015 17:50:00 Z

Thanks! I appreciate all the help.

guest — 4 Jun 2015 17:35:00 Z

Steve, You can run the profiler or in the case of the express version just download expressprofiler or some other tool like tha…

guest — 4 Jun 2015 17:16:00 Z

something like: HDescribeConnection("mssql",G_USERDB,G_PASSWORDDB,G_SERVERDB,G_DB,hNativeAccessSQLServer,hOReadWrite,"WD Connec…

guest — 4 Jun 2015 16:43:00 Z

Quote Paulo Oliveira if you want to have the same behavior as the oledb use WD CLIENT VERSION=2000 Thanks Paulo, how …

guest — 4 Jun 2015 16:35:00 Z

if you want to have the same behavior as the oledb use WD CLIENT VERSION=2000

guest — 4 Jun 2015 16:18:00 Z

I'm using 32 bit and sqlncli 2008.

guest — 4 Jun 2015 15:04:00 Z

Steve, Are you using 32/64 bits? If in 32 bits did you test with sqlncli or dbnetlib? If you are using sqlncli what is the ve…

guest — 4 Jun 2015 07:58:00 Z

I'm wondering if the pre-release SQL Server Native Access for WD 20 is wanky.

guest — 4 Jun 2015 06:58:00 Z

Jorge, the application was originally written in Postgres with native access and then migrated to MS SQL when we took it to mark…

guest — 4 Jun 2015 03:56:00 Z

Hi, We use WD + MS SQL several years, with connection with OLEDB provider. Why Native Access for MS SQL? If for ompatib…

guest — 4 Jun 2015 02:31:00 Z

Hi I've been running sqlServer12 (64-bit on Windows764-bit) from wb/wd17-19 with a charm. Pls check if your installations…