We have a command line utility whose main PRG calls everything inside of a TRY/CATCH block. The CATCH clause would take any error and dump the info to a file, so as to avoid any popup interactive error dialogs. However, we've run into a problem where a dialog still pops up.
Given the user's passed parameter, the utility will open up a hidden form to execute some of its methods. If the user's database is not in sync with the form's data environment (e.g. table isn't in database because they haven't updated their data structures), then the Locate Database dialog pops up stating that there was an error instantiating the cursor object. If this is all inside of a TRY/CATCH block, then why isn't this error being trapped like all the others?
Laterness,
Jon
Jon Rosenbaum
Devcon Drummer