I work for a software development company, we are currently working on a project that utilizes VB6 and SQL Server.
We had a very obscure 'DLL' type error which was difficult to diagnose because it returned no traceable errors within VB.
Criteria of the problem: Only using runtime, can not replicate using the IDE.
The problem: Function ONE runs through a list of records in SQL Server. Depending on the type of record, a sub-function is called - we'll call it sub-function TWO. Now here is where it gets wierd.
Within sub-function TWO calling other functions and returning works fine, but when I open an ADO recordset and BEFORE doing the ADO update, I run another function - the entire 'chain' of functions crash. Example:
ADO.ADDNEW
ADO![Description] = subfuncDESC(strPART)
ADO.update
So the primary Function ONE calls function TWO, which does calls other minor functions. But when I call a minor function within TWO in between an ADO addnew / update it crashes.
The crash it causes is non-trappable within VB and it looks like the functions just all simultaneously stop. Due to the fact it only happens on client installations.. we suspect it to be some kind of DLL error or MDAC...
We were in a panic when this bug hit us, so to resolve it, we crammed all the minor function calls of TWO directly into TWO using Gosubs
Has anyone else had such an obscure problem like this?
We had a very obscure 'DLL' type error which was difficult to diagnose because it returned no traceable errors within VB.
Criteria of the problem: Only using runtime, can not replicate using the IDE.
The problem: Function ONE runs through a list of records in SQL Server. Depending on the type of record, a sub-function is called - we'll call it sub-function TWO. Now here is where it gets wierd.
Within sub-function TWO calling other functions and returning works fine, but when I open an ADO recordset and BEFORE doing the ADO update, I run another function - the entire 'chain' of functions crash. Example:
ADO.ADDNEW
ADO![Description] = subfuncDESC(strPART)
ADO.update
So the primary Function ONE calls function TWO, which does calls other minor functions. But when I call a minor function within TWO in between an ADO addnew / update it crashes.
The crash it causes is non-trappable within VB and it looks like the functions just all simultaneously stop. Due to the fact it only happens on client installations.. we suspect it to be some kind of DLL error or MDAC...
We were in a panic when this bug hit us, so to resolve it, we crammed all the minor function calls of TWO directly into TWO using Gosubs
Has anyone else had such an obscure problem like this?
