General information
Title:
Debug_logme.prg (helps find code)
Environment versions
Network:
Windows 2008 Server
The attached file is a program I use called debug_logme.prg. It helps me quickly track down where in some foreign program something is happening.
For example, if I need to know, "Where in this application is the record being added to table X?" I go in to table X and add an insert trigger which is "debug_logme('Tracking down insert record')" and then I go into the application and add a record. If I need to know, "Where is a particular column being updated?" then I add it to the column trigger and go into the application and do the operation which updates the column. Afterward I can examine the debug_logme.dbf table it creates, and it shows me the complete stack so I know where everything came from.
I have found this kind of helper to be a great time saver in tracking down code issues. You can insert it anywhere, but I mostly use it on table or field triggers to find out where a particular table or column is being affected.
Please report any bugs if you like. Thank you.
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only