Hi Dragan,

thank you for your comments. Unfortunately I have tried all of this already,

Usually I work with 2 or copies of VFP, so I am eventually running into situations, where VFP is not happy with my actions. As I have automated most of the needed actions I can quickly shut down everything and restart my 2 or 3 instances. There have been situations, where it is better, to have only one instance running, when I do development work. Therefore has become a standard remedy procedure for me, to shut down every instance, open only one, recompile everything (even classlibs, which include are not included themselves, but contain parents of those classes, which are included in the project), build up the project from scratch (after deleting the old one) and so forth. This has helped always, but not this time.

Coming back to the case on hand: Presently I am assuming, that the debugger can only grab source code, which is already available in the items included in the project. Source contained in methods of objects, which are instantiated at run time, may not be available to the Debugger, though the classlibs are part of the project, located on the same machine and having been recompiled shortly before.

One Example: In my case, there are objects, which are added to the form mentioned in the Form Designer. Their code is shown by the Debugger. But I have a few objects, which are added at run time and which are instantiated from UserDefinedClasses contained in UserDefinedClassLibs, which themselves are included in the project (see my code example).

After removing the usual bugs the app works fine. This is - in my opinion - the proof, that the source is available. So why does the Debugger not find it?

Greetings

Hans

>>... this is exactly what puzzles me: The source of UserDefinedClass (there has been a typo in my previous message) is accessible at least when the form runs. To prove, whether I have access to the source of that class, I issued
>>

MODIFY CLASS UserDefinedClass of UserDefinedClassLib.vcx

>>in the command window and I had immediate access to the UserDefinedClass and all of its source.
>>
>>So there is still a gap in the reasoning, why the debugger cannot have the same access.
>
>I've seen situations when the code should be available to the debugger, but somehow isn't. Could be the timestamps inside the classlib don't match what's in the project file or the datetime of the vcx/vct file itself.
>
>One thing I'd try (not sure it'll work - the "source unavailable" is quite a stubborn animal) is to compile classlib, quit Fox, try again. This would also fix it in case the classlib was last compiled in a different version of Fox (not sure that may be the cause at all, but who knows - I never have the patience to investigate this :).
>
>There may be other things as well that may cause the debugger to treat this class as sourceless, I haven't found them all yet, because this doesn't really happen to me that often.