We of course changed source to 32 bit when we went to 32 bit ODBC drivers.
Did not try pypyodbc and did not know about pytds, which is cool to know!
Thanks. For now we have a solution so my message is to just try and save
folks a lot of time and grief.
--
Resources:
- http://web2py.com
-
Right, I'm using Windows 2012 64bit and MSSQL 2012 on cloud. Tried python
64 bit with pyodbc first then go back 32 bit. It works fine.
On Tuesday, January 13, 2015 at 6:06:37 PM UTC-6, Pbop wrote:
Spent days trying to track down an error with a Web2Py app and SQL Server
2008 R2 running 64
first and foremost, web2py doesn't need an odbc source defined at system
level.
That being said, it can, but if you're running the source with a 32-bit
python or the executable (32-bit too) it's pretty obvious that a 64-bit
defined odbc source won't be available...
On Wednesday, January 14,
So have you tried to use pypyodbc? If that doesn't work, you could use
pytds and bypass odbc altogether.
On Tuesday, January 13, 2015 at 5:06:37 PM UTC-7, Pbop wrote:
Spent days trying to track down an error with a Web2Py app and SQL Server
2008 R2 running 64 bit ODBC drivers.
Switched to
4 matches
Mail list logo
