VB6 Lost Code - DLL Help [modified]
-
We have a VB6 DLL in production, but, the source code that can be found is missing a function found in the DLL. The source code has sections of hard-coded SQL statements that are used to extract data from a legacy system (Ingres II). All I really need is the SQL statements for the missing function. Does anyone know of a way to open and read the DLL? I have tried notepad, but, it doesn't appear to show me the missing section. Yes, the code SHOULD have been replaced in SourceSafe, but, it wasn't. And, the 3 most likely developers left the company some time ago. Thanks, Tim
modified on Wednesday, October 8, 2008 11:42 AM
-
We have a VB6 DLL in production, but, the source code that can be found is missing a function found in the DLL. The source code has sections of hard-coded SQL statements that are used to extract data from a legacy system (Ingres II). All I really need is the SQL statements for the missing function. Does anyone know of a way to open and read the DLL? I have tried notepad, but, it doesn't appear to show me the missing section. Yes, the code SHOULD have been replaced in SourceSafe, but, it wasn't. And, the 3 most likely developers left the company some time ago. Thanks, Tim
modified on Wednesday, October 8, 2008 11:42 AM
Just a thought - If the SQL was MS SQL2000, I am pretty sure you can use SQL Profiler to dump all sql queries run on the database, which would show the queries actually run by the DLL... Sql Profiler may be availiable for other DBEngines, but I have only used the one in SQL2000.
-
We have a VB6 DLL in production, but, the source code that can be found is missing a function found in the DLL. The source code has sections of hard-coded SQL statements that are used to extract data from a legacy system (Ingres II). All I really need is the SQL statements for the missing function. Does anyone know of a way to open and read the DLL? I have tried notepad, but, it doesn't appear to show me the missing section. Yes, the code SHOULD have been replaced in SourceSafe, but, it wasn't. And, the 3 most likely developers left the company some time ago. Thanks, Tim
modified on Wednesday, October 8, 2008 11:42 AM
You're best option is to run a tool like SQL Profiler which can show you all of the active database connections and the SQL statements being performed. SQL Profiler specifically is only available for Microsoft SQL Server, but Ingres should have something similar. Red-Gate may also have a similar tool that will work as well.
Scott Dorman
Microsoft® MVP - Visual C# | MCPD President - Tampa Bay IASA [Blog][Articles][Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
-
We have a VB6 DLL in production, but, the source code that can be found is missing a function found in the DLL. The source code has sections of hard-coded SQL statements that are used to extract data from a legacy system (Ingres II). All I really need is the SQL statements for the missing function. Does anyone know of a way to open and read the DLL? I have tried notepad, but, it doesn't appear to show me the missing section. Yes, the code SHOULD have been replaced in SourceSafe, but, it wasn't. And, the 3 most likely developers left the company some time ago. Thanks, Tim
modified on Wednesday, October 8, 2008 11:42 AM
Ack what a head ache. Profiler could work to get the queries, but of course requires that you know how each part of the logic is called to hit all the different queries/statements. I feel for ya.
Any suggestions, ideas, or 'constructive criticism' are always welcome.
-
We have a VB6 DLL in production, but, the source code that can be found is missing a function found in the DLL. The source code has sections of hard-coded SQL statements that are used to extract data from a legacy system (Ingres II). All I really need is the SQL statements for the missing function. Does anyone know of a way to open and read the DLL? I have tried notepad, but, it doesn't appear to show me the missing section. Yes, the code SHOULD have been replaced in SourceSafe, but, it wasn't. And, the 3 most likely developers left the company some time ago. Thanks, Tim
modified on Wednesday, October 8, 2008 11:42 AM
For those that tried to help, thank you. If this was a SQLServer database, I could have used Profiler, unfortunately, this is an Ingres II database (legacy, text only environment). So, since I could see the data for process was generating (the DLL was storing data in SQLServer), I talked to the people working on the legacy system and showed them the data. From there, I slowly rebuilt the query to produce identical results. The new query is stored in a table in SQLServer; the DLL will call a stored procedure that returns an SQL statement. If the source data changes, SQL changes are then made in SQL, not in the code itself. Thanks, Tim