Ain't that the truth, Dennis! Can't say I remember 100% of the time, but I always try to put a comment at the top like:
-- on Row Entry of the Invoice table (these in particular seem "hard to find") -- on exit of the InvoiceNo field -- on Form After Start Karen -----Original Message----- From: Dennis McGrath <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wed, Jul 3, 2013 12:54 pm Subject: [RBASE-L] - Re: mystery eep It's always a good idea to put a comment at the top of every eep identifying it explicitly. Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Wednesday, July 03, 2013 12:49 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: mystery eep Dick, It's possible that you have the EEP as a row event which wouldn't show in your search. You need to specifically look at the code just before you jump to the EEP with a number. Jan -----Original Message----- From: Dick Fey <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Wed, 03 Jul 2013 12:41:13 -0500 Subject: [RBASE-L] - mystery eep > Having a very strange problem. > > A form that sends emails has been acting up. > When you trace it, it seems to do the print command properly, goes to > the return, then calls an eep that is NOT in the form. > Checking under Edit , Find in Custom EEPS, Nothing shows up that > contains the lines that occur in the EEP. > In trace, the eep seems to be in an endless loop. It keeps recalling > itself. It has a number that shows in the trace, but I have no idea > where to > look for it using that number. > > Any good clues ? > > Dick Fey > Carpet Broker Inc. > >
