Looking for the latest version? Download ODBCQueryTool_1.0.4.rar (980.7 kB)
Home
Name Modified Size Downloads / Week Status
Totals: 2 Items   2.1 kB 2
odbcquerytool 2011-03-04 122 weekly downloads
readme.txt 2011-03-04 2.1 kB 22 weekly downloads
Version 1.0.4. (Build: 34) - Solution for some XP computers giving streaming-errors at startup. Due to incorrect optimalisation settings in some source files in the project and a MSVCRT dependency in the installer. - This is a servicepack for the retracted 1.0.3 version Version 1.0.3 (build: 33) - VERSION REMOVED. BLOCKING BUGS ON MS-WINDOWS XP - Recurse to Windows Version 5.xx in Stdafx.h because of support problems with Windows-XP (fonts and SHGetFolderPath) Tested on XP-Mode in 32 bits mode, and works fine Version 1.0.2 (build: 32) - New routine to do the discovery of %APPDATA% and so safe your connections on MS-Vista and Windows-7 in the correct way - Fonts of connection dialog and query result grid can be chosen Misfits on some XP machines to fonts smaller than 4 px Make your choise at the menu "Text / Permanent settings / Query setttings" - For the rest of the version history: see the "history.txt" file in the distribution. This is the README for ODBC QueryTool This ODBC Query tool is meant to be used against ODBC datasources. It's primary purpose was to test various SQL commands againt an ODBC connection instead of an Oracle OCI connection. This was needed because 1) Specific ODBC SQL could be tested like "{ oj ... }" outer join syntax 2) Specific escape sequences could be testen like "{ fn ...}" syntax 3) General proof that a command does work against an ODBC connection 4) General proof that the ODBC connection does work More general: nowdays every database tend to come with it's own administration and query tools, which means that a user has to have knowledge of all seperate tools and interfaces. This tool provides 1 (one) interface for a general ODBC database, so that a user only needs one tool to learn. The downside of this choice is that the more sophisticated administration tasks cannot be administred right away other than by typing SQL. There are no fancy dialogs to administer database dependent objects like stored procs and such. The good thing about this is that the user gets to know their database pretty well.
Source: readme.txt, updated 2011-03-04