>
>Well, I THINK it is normal.
>
>Doing the TableUpdate() one record at a time (using GetNextModified() to find modified records), might help you show a progress indicator (might be as simple as a WAIT WINDOW, or one of the progress bar downloads). I do hope that this doesn't significantly slow up the whole process.
>
>One more thing: one thing you might want to check is, do the updates in the table trigger updates in other tables. This will make a TableUpdate() slower than if there are no such updates. For example, if you keep an audit trail, a change to any record will trigger changes to the audit table. Or, updates to a product reception/dispatch might trigger changes to the current stock in the product table.
I believe that showing
one WAIT message will suffice. I didn't have ANY messages before that caused the problem. So by putting
A message I am improving the code 100% <g>.
And in my program, there is not audit trail or other tables being updated. So it is the fact of 130,000 records written at the same time takes so much time.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
