>>>>That's wrong again. I think, when you use AGAIN you have to use different alias.
>>>>
>>>Not true, VFP create a name for you!
>>
>>Doesn't matter, it still would not be STUD < g >. You have to close that newly opened table, not the originally opened STUD.
>
>And the code do this!
>
>Update: except a copy/past error :)
>

>select 0
>USE Stud AGAIN
>APPEND FROM DBF("csrCourseStats")
>USE
>

I was reading this thread and thinking how much simpler this is that checking to find if the table was open, etc.

Then I had a different question about an area I don't thoroughly understand.....

Let's say that Stud is currently open. You open it AGAIN, append the records, and close the second version.

What problems might there be reflecting the appended records back to the original work area with each of the various buffering options? Or if you have a transaction running? If you close the first one, are there any chances that you could lose the appended records?

My applications have never approached this level of complexity, but I'd like to be ready if they do.

Thanks........Rich