Hi Everyone,
Is there something wrong with the MSSQL driver in build 13505? I have an app that has multiple exes. All but one exe uses FM3 to connect to the MSSQL backend.
All exes are working correctly in build 13372.
As soon as I upgrade to build 13505 the exe that doesn’t use FM3 to connect to the MSSQL backend stops connecting. The connection window just hangs and I have to use Task Manager to kill the exe. All FM3 exes connect successfully.
I’ve tested creating a new app with the exact same code and in build 13505 and it works correctly. What could be going wrong in the existing app? The code being used is pretty much the same as the FM3 code so I’m not sure why this problem is occurring.
Any ideas?
Also can someone post this in the C11 newsgroup for me? For some reason I can’t post to any newsgroups anymore.
Regards,
Trent
Not having connection problems, but 13505 definitely brought problems with PostgreSQL tables having an array. The version did include changes to the ODBC driver.
I am having the same issue Trent, don’t have time to investigate, so just rolled back to 13372
Hopefully they can fix it in the next build. I’ll add a bug to the problem tracker.
did You use a connection string like this? :
tcp:myserver,port
In my environment i am having problems connecting this way, because the owner attribute is separated by commas as well:
“server, database, uid,pwd;LANGUAGE=language;APP=name;WSID=name”
Something changed in 13505 that causes that if you connect too early to MSSQL. I had the same problem in a multi-dll solution, you can read SV comments in PTS #43043.
Capesoft worked around this in FM3
Version 5.49 GOLD (13 August 2020)
…
Work-around for Clarion 11 release 13505 that inits runs the data DLL init section too early. You need to check the “Init FM3 in the ‘Initializing other ABC Clarion DLL’ embed (recommended for Clarion 13505 an up)” setting in the FM3 global template.