The object browser does not show when connecting to SQL Server 7 systems. QueryEx Plus also has this issue - see attached video - not sure if it's a bug or protocol change.
Dear Zack, thank you for posting the first QueryPony issue!
I have no SQL Server 7 available to debug the matter, but I have a suspicion:
The connection is made via classes from the .NET System.Data.SqlClient namespace. The MSDN documentation http://msdn.microsoft.com/library/system.data.sqlclient%28v=vs.90%29.aspx says "Caution ADO.NET 2.0 does not support asynchronous commands over shared memory for SQL Server 2000 or lower. However, you can force TCP instead of shared memory. You can do that by prefixing tcp: to the server name in the connection string or you can use localhost.".
This sounds, as if you can connect to SQL Server 7 by using the TCP/IP protocol instead of the default shared memory protocol.
Please try the TPC/IP connection, perhaps it applies for you.
If TCP/IP does not work for you, your chances look grim. The issue seems not to be a bug but a protocol change -- the introduction of shared memory usage after SQL Server 7.
In case you (or anybody else) want delve into the debugger, that will demand some project tweaking due to the single-file-delivery feature, which must be switched off to make Visual Studio or SharpDevelop break at the relevant lines (see http://querypony.sourceforge.net/developing.html subchapter 'Project Settings'). If anybody attempts to debug, of course I try to assist.
Thanks again,
Norbert
Last edit: Norbert C. Maier 2020-05-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Zack, thank you for posting the first QueryPony issue!
I have no SQL Server 7 available to debug the matter, but I have a suspicion:
The connection is made via classes from the .NET System.Data.SqlClient namespace. The MSDN documentation http://msdn.microsoft.com/library/system.data.sqlclient%28v=vs.90%29.aspx says "Caution ADO.NET 2.0 does not support asynchronous commands over shared memory for SQL Server 2000 or lower. However, you can force TCP instead of shared memory. You can do that by prefixing tcp: to the server name in the connection string or you can use localhost.".
This sounds, as if you can connect to SQL Server 7 by using the TCP/IP protocol instead of the default shared memory protocol.
I experimented with the TCP/IP connection to a SQL Server Express 10.0 and documented the session in a preliminary QueryPony manual page http://downtown.trilo.de/svn/queryponydev/tags/20180819o2344.trunk.v0.3.4/QueryPony/QueryPonyGui/docs/20140127o0511.mstcp.html .
Please try the TPC/IP connection, perhaps it applies for you.
If TCP/IP does not work for you, your chances look grim. The issue seems not to be a bug but a protocol change -- the introduction of shared memory usage after SQL Server 7.
In case you (or anybody else) want delve into the debugger, that will demand some project tweaking due to the single-file-delivery feature, which must be switched off to make Visual Studio or SharpDevelop break at the relevant lines (see http://querypony.sourceforge.net/developing.html subchapter 'Project Settings'). If anybody attempts to debug, of course I try to assist.
Thanks again,
Norbert
Last edit: Norbert C. Maier 2020-05-23