Yeah, that's basically it. The trouble is balancing giving enough information without giving too much. I try to pare things down to exactly what I need so I don't flood the helper with irrelevent info. I guess I pared too much. :)

Here's the situation:

SBT has a UDF to lock a record called g_lckrc. This function is in with a bazillion other functions in SBTPROC. In g_lckrc, it checks to see if the passed table is at EOF(). If so, it calls yet another function to display an error. At no time is ON ERROR tripped. This is strictly SBT's error checking.

Sometime during the process of "shipping" sales orders, it comes up saying "EOF() on record lock attempt". I can see where in g_lckrc it checks if the passed table is at EOF(), but I have no idea which call to g_lckrc is triggering it.

So _somewhere_ in that vast mess of SBT code, it tries to lock a record while at EOF(). I'm trying to figure out _where_ so hopefully I can figure out _why_.

I'm hoping that it's the same code each time and that there's a bug in the code rather than something else influencing it. If that's the case, then knowing what line g_lckrc is being called from will help me. If not, then I don't know what I'm going to do, yet. :)

Is that clearer, now?

Thanks very much for your patience and your help,

Michelle


>Michelle,
>
>Sorry, didn't realize what you were dealing with here.
>
>I think, however, part of the confusion here may be that folks don't really understand the problem. In my case, the "lightbulb" just went on. If you don't mind, let me parrot it back to you, and maybe one of us (not necessarily me) might come up with a solution. If I'm incorrect at any point, please clarify.
>
>A particular method is triggering the error handler.
>
>This method is called from another method, and the error is being caused by either a bad parameter list, or an improperly set property being referenced within the receiving routine.
>
>The method calling the one causing the error calls it 19 or 20 times within the body of it.
>
>Is this right? BTW, you've never mentioned what the error is. It might be helpful.