Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Son of Accused of Violations I'm not committing
Message
De
24/03/2005 07:32:22
 
 
À
23/03/2005 17:15:55
Dragan Nedeljkovich
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Versions des environnements
Visual FoxPro:
VFP 7 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
00998499
Message ID:
00998799
Vues:
18
>Instead of trying to guess where it happens, why don't you just suspend when it happens, open the debugger, and trace back to the offending command? AStackInfo() would help, too.

As I said before, the error occurs, esp. with a particular record, which isn't a duplicate, at the following line: either at the "With thisfile" or before .lmCompileReport(), i.e. nowhere on an executable line that does anything that would upset RI. AStackInfo() merely tells me that I'm on the printing form and that I've invoked the .click(0 of the button - nothing else.

This has got to be the most bizzare error I've ever had!

Preview button click method:
With thisform
  .lmCompileReport()
  .cmdCancel.caption = "\<Close"
  .Visible	   = .F.
  Report Form serRouteIndex Noconsole preview
  .Visible	   = .T.
EndWith
If I put a breakpoint on "With thisform", and during the run, click the button, then the err. mess. occurs sort of at the same time as debug is invoked. A window (presumably debug) flashes on and off before I can see it, the error messag pops up. When I dismiss it (it only has OK or Help buttons), and open debug, the cursor is either on "With thisform" or sitting waiting to do ".lmCompileReport()"

Any ideas, experience of similar?

Terry
- Whoever said that women are the weaker sex never tried to wrest the bedclothes off one in the middle of the night
- Worry is the interest you pay, in advance, for a loan that you may never need to take out.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform