Forgive me but, although VB6 was my bread and butter once,I have not touched it in over 10 years and I have never dealt with groups that contain multiple projects. Nor have I ever been much of an "object orientated" man so I have little experience with classes.

I have been asked to investigate some problems with such a project group. I have successfully added all the projects (which, when compiled, generate a number of DLLs and EXEs) to a group and I can certainly trap issues within the development environment by setting debug break points in some of the projects but not all.

I have sucessfully added code that sends progress messages to a log file and here is an example as to where I'm getting a problem.
Code:
Public Sub TriggerMaster()
        
On Error GoTo ErrorTriggerMaster

GmsLog ("Pre class")
        Set fred = New clsFred

GmsLog ("Pre object")
        Set RunNow = CreateObject("projJohn.clsJohn")

GmsLog ("Pre execute")
         RunNow.Execute False, fred

GmsLog ("Complete")
This code is debuggable interactively step by step and a type mismatch error is triggered after the "Pre execute" message has been successfully logged suggesting that the mismatch is in the RunNow.Execute. What I am pondering now is whether that is a problem with the line itself or with The RunNow execution (ie logiv within its Execute method)? RunNow is within the project group and is an EXE. It does not seem to be accessible for debugging when running interactively and even if I add message logging and recompile the EXE, it does not generate any of the messages I might have expected to see.

Can anyone offer any tips as to what the problem might be and/or how I might debug this more productively? Might removing the RunNow exe trigger interactive debugging in the RunNow project?

Any help would be greatly appreciated, thank you.