Bob_Hansen
Senior Member Members
    Offline
 WOW, They have the Internet on computers now!
Posts: 1861
Location: Salem, NH
Joined: Nov 24 th, 2002
|
[Solved] "Hidden" programming?
Oct 13th, 2007 at 5:31pm
|
Print Post
|
Solution: Compile errors that appear when opening a Form that has subforms may actually be in the code behind one of the subforms.
I am using 2.03, application with about 15 databases, most were merged from Q&A databases, have hundreds of reports, specs, etc.
I keep getting error message in Preview Mode, and in normal mode, for one form. Error message says compile did not complete....... This happens when opening form in Add mode, in Search mode. When I open program Editor, test passes, but I went and commented out all programming. I also commented out Application programming. Many of the other forms open with no problem.
Then I remembered about an earlier import XML problem that was based on programming in Mass Update. So, I looked at Mass Update Specs, found about 10, deleted about six, kept the other four and commented all of their programming. No change, still getting same error. Many elements referred to in the Update Specs referred to elements that were removed after merge process.
I am now looking at the possibility that perhaps programming in Saved Retrieve Specs and/or Reports might be causing this error? How to easily troubleshoot this? I am thinking of copying the database, then deleting all reports and all Retrieve Specs to see if that removes the problem. That would provide a proof of concept that the problem is somewhere in there.
And if that does remove the problem, that means I will need to open each single Retrieve Spec and/or Report and look for any programming that may be in conflict. I am sure that there are probably some Retrieve Specs and Report elements that are referencing elements that have been removed. Note, the original fields still exist in the database, but not bound to form elements, to be removed in the future, but not until sure they are not needed.
I spent all last weekend on lost time because I did not remember some command (already forgot what it was). Decided to ask for help before I lose another weekend, taking the long route vs. a shortcut. (Aha, just remembered what I forgot, an array list of all reports could have been used).
Cannot even test the form in Preview mode right now. So, any ideas on a simple way to isolate and correct this error message?
|