>>>>>BUT you must have project and run application from it, not the compiled EXE.
>>>>
>>>>How do you come to that conclusion?
>>>>It works for compiled exe, but the exe should be located alongside the pjx, or you may not see some code. It's also a good idea to have debuginfo turned on on projectinfo (righclick the project manager.)
>>>
>>>ASSERT do not work in EXE.
>>
>>Wrong again. ASSERT runs pretty well inside exe as long exe is inside IDE. If outside ASSERT is like NOTE.
>
>I don't see reason to run exe inside IDE, I just run the main program in the project :-)
>And BTW you SHOULD have a pretty good log when error happens when the exe is running outside the IDE.
Common log is around 75k / 1200 lines, listing all cursors in all datasessions with reccount, recno eof bof buffer stype dbf, active alias per datasession transaction level databases and active database active filter / order with available info on tag per cursor, variables, disp stat, properties of app object, object with failure, its superparent (for example: form), computer, application, verno of app, OS user loggged on to both app and system, DLLS, Filehandles, Windows
Would that suit you?
BTW this comes up on every error, even on testing. Ah, it's in a dbf itself, I can go back ....
:)
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]