>>... I ran across this at my current client's location, and came up with this fix. It involves adding code to the Error() method of cDataEnv's cDataEnvironment class. Here is the code for that method:
>>
>> FUNCTION Error(nError, cMethod, nLine)
>> IF nError = 1709
>> * DBC in use error
>> SET MESSAGE TO "DBC in use; please wait..."
>> * Pause for a brief instant before retrying
>> =INKEY(.1)
>> RETRY
>> ELSE
>> ERROR(nError)
>> ENDIF
>>
>> RETURN
>> ENDFUNC
>>
>> What this does is trap the "DBC in use" error and pause briefly before retrying to access whatever information it needs (usually a view definition).
>>
>>José
>
>Thanks for the reply. This is the first thing that I tried (with and without the INKEY), and it is what results in the Pushjmp /Popjmp error.

Erik,

Never heard about the Pushjmp/Popjmp thing. You might want to talk to Ed directly. He does not monitor this forum, but you'll find his email on my web.

I read your other messages and was wondering if you might have something wrong with your DBC. If you have an external utility to rebuild it, that's certainly something that I would try.

José