Create and deliver personalized experiences across digital properties at scale
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Transform your businesses in order to survive in a completely digitized and connected world driven by software innovation.
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
I recently read a blog entry where the author went to great lengths to explain what he did to make an application originally compiled as 64-bit for production deployment onto a 64-bit Windows platform work with the the 32-bit ODBC driver that he was using. My reaction, well, yeah, that's one way to solve your problem, but I'm mystified why the most obvious route to solving the problem - simply using a 64-bit ODBC driver - wasn't chosen.
There may be valid reasons which were not called out for why the author did not choose this route, but consider this:
An easier way to solve this problem would be to acquire the 64-bit version of the ODBC driver being used. Details on how to get the 64-bit version of the Progress ODBC driver for Windows is available in the Progress Knowledgebase.
Finally, it's worth noting that DataDirect offers products which can serve to connect 64-bit applications and 32-bit ODBC drivers without the need to recompile and introduce inefficiencies and performance bottlenecks. This is useful for situations when there is no 64-bit version of the ODBC driver available, which is common when one is connecting to legacy data sources or ones that are no longer being supported.
Conclusion: just like Occam's Razor suggests, the simplest solution to this problem is the best.
View all posts from Mike Frost on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.