Hi Nadya,

That's pretty weird. Hard to guess why it would be related to a TableUpdate() per se. About all I can tell you is that the name of the variable in question (OPROGRESSBAR_0L10SJAYO_PERCENTLABEL) is coming from the underlying class code for progressbar in commctrl.vcx. If you look at that code you'll find that he does

THIS.PercentLabelName = THIS.Name + Sys( 2015) + "_PercentLabel"

All that tells me at the moment is that that's where the name is created, but it's a start.

The error message you're seeing is evidently coming from an error handler of some kind. Can you pin this down to the particular line of code that's running at the time, or do you already know that it's a TableUpdate() command?

I have to add that years of teaching and debugging, including debugging my own work, have taught me to always investigate comments such as "...using your ProgBar with my minor unrelated modifications". I'm sure you know what you're doing, but you may want to double-check those modifications just to be sure they're really unrelated to this problem.


>Hi Rick,
>
>We're trying to investigate some TableUpdate Error. One person is doing Address Standardization. The table is table buffered. I run scan through the file and show Progress bar using your ProgBar (with my minor unrelated modifications). After the process is finished I call oProgBar.Release(), then release oProgBar. Then there are few other lines of code and then cmdAdd.click, which does tableupdate. The other person is doung manual link in the same time on the same file. This application uses record-level buffering. They both got an error. The first person got this error:
>

>The following Errors have been reported by tableupdate():
>
>Error num: 12
>Error Message: Variable 'OPROGRESSBAR_0L10SJAYO_PERCENTLABEL' is not found.
>Error Parameter: OPROGRESSBAR_0L10SJAYO_PERCENTLABEL
>Alias : G:\REDP\WORK\TP\CT\TPCT200147_B.DBF
>Record Number : 18

>
>The other person got VFP error "Update conflict". So, we're trying to investigate the problem. We were able to re-create the same error (but not the Update conflict). So, does it mean, what oProgBar was not released for some reason?
>
>I can not reproduce this error in standalone tests of this application...
>
>Thanks in advance for any clues.