Release 3.5.5 - 32 Bit Executables missing

[GStegemann]

Hi Edwig,

are there any specific reasons why you didn't release the 32 Bit Executables of ODBCQueryTool? Can they still be build?

Best regards,
Gerhard

[edwig]

There is no specific reason why there are no more 32bits executables, other than that the world has turned fully to 64 bits. Frankly this is the first post where they are requested. But of course: they can still be build. Just grab the source and create the 32bits configuration in Visual Studio as a copy from the 64 bit versions and hit the 'build' button.

[GStegemann]

I understand your point. But the world has not fully turned to 64 bits yet. I'm still working on projects which require the 32 bit ODBC platform.

However, it seems to be not so easy to create the Win32 build configuration. I followed your advice. But it was not possible to change the platform of component StyleFramework to Win32. After changing the platform in Visual Studio Configuration Manager it flips back to x64.

I would suggest that you keep the Win32 build configurations for a while.

[edwig]

I really hate to wake you up to the fact that the world has moved on. No OS is to be gotten in 32bits (Windows, Linux, Mac OS). Me myselft have stopped using and building 32bit software 10 years ago. All software including MS-Office is to be downloaded and used in 64 bits form.
This project is really going into the other direction. Instead of creating more variations and builds, all projects and underlying libraries are moving into the direction of 64bit Unicode aware modern C++ (ISO standard 17 and above). So very soon I will even drop the ANSI builds in favor of the Unicode builds.

So, I'm really sorry!!
I will not again be building 32bit releases of this software.
The next release will contain a "Deprecated message" for the ANSI version as well.

[GStegemann]

You don't need to wake me up. I really know that the world has moved on to 64 bit software. But there are industries or businesses that cannot upgrade their applications to 64 bit versions due to compability issues. That is also reality. And I'm supporting such applications.

However, if you plan to drop also the ANSI versions the ODBCQueryTool becomes useless to me. And I have to look for alternatives.

But allow me one more question: Since I have to build the 32 bit version of ODBCQueryTool by myself is it possible to build also the module StyleFramework as Win32? Or do you have any advice how to do configure the build of StyleFramework?

Best regards,
Gerhard

[edwig]

OK. After some investigation, it is not possble to revert a project file to "Win32" (the 32bits variant).
So I did hand-crafted this change and tested it in the "StyleFramework" project.
Here is the result. Just download it and rename the *.XML to *.vcxproj

You should be able to drop it into the ODBCQueryTool solution in the "StyleFramework" directory and then reconfigure for "Win32" / X86

Have fun!

StyleFramework_win32.xml

[GStegemann]

Many thanks. I will try it tomorrow.

[GStegemann]

I tested your project file.

However, I had to change two settings:

• PlatformToolset to v143. I guess v145 is the default of Visual Studio 2026
• the ItemDefinitionGroup was mising for build "Release|Win32". I added that.

Could you view my settings in the added ItemDefinitionGroup:

<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"> <ClCompile> <WarningLevel>Level3</WarningLevel> <Optimization>Disabled</Optimization> <SDLCheck>false</SDLCheck> <PrecompiledHeader>Use</PrecompiledHeader> <AdditionalIncludeDirectories>$(SolutionDir)StyleFramework\Grid</AdditionalIncludeDirectories> <RuntimeLibrary>MultiThreaded</RuntimeLibrary> <PreprocessorDefinitions>WSCALE;_MBCS;%(PreprocessorDefinitions)</PreprocessorDefinitions> <LanguageStandard>stdcpp17</LanguageStandard> <RuntimeTypeInfo>true</RuntimeTypeInfo> <LanguageStandard_C>stdc17</LanguageStandard_C> </ClCompile> <Lib> <OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile> </Lib> </ItemDefinitionGroup>

Then the builds passed without errors.

[edwig]

Good on you!Congratulations!!Verzonden vanaf Outlook voor AndroidVan: Gerhard Stegemann ***@***.***>Verstuurd: dinsdag, februari 17, 2026 1:19:50 p.m.Aan: edwig/ODBCQueryTool ***@***.***>CC: Edwig Huisman ***@***.***>; State change ***@***.***>Onderwerp: Re: [edwig/ODBCQueryTool] Release 3.5.5 - 32 Bit Executables missing (Issue #19)GStegemann left a comment (edwig/ODBCQueryTool#19)I tested your project file.However, I had to change two settings:PlatformToolset to v143. I guess v145 is the default of Visual Studio 2026the ItemDefinitionGroup was mising for build "Release|Win32". I added that.Could you view my settings in the added ItemDefinitionGroup:<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"> <ClCompile> <WarningLevel>Level3</WarningLevel> <Optimization>Disabled</Optimization> <SDLCheck>false</SDLCheck> <PrecompiledHeader>Use</PrecompiledHeader> <AdditionalIncludeDirectories>$(SolutionDir)StyleFramework\Grid</AdditionalIncludeDirectories> <RuntimeLibrary>MultiThreaded</RuntimeLibrary> <PreprocessorDefinitions>WSCALE;_MBCS;%(PreprocessorDefinitions)</PreprocessorDefinitions> <LanguageStandard>stdcpp17</LanguageStandard> <RuntimeTypeInfo>true</RuntimeTypeInfo> <LanguageStandard_C>stdc17</LanguageStandard_C> </ClCompile> <Lib> <OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile> </Lib> </ItemDefinitionGroup>Then the builds passed without errors.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.