Denise,

You might have missed it in the answers to your prior post. But the best way to analyze a Tableupdate() command to to look at the results using Aerror(). This will give you the reason for the failure.

PF

>Thanks for the help on the tableupdate() problem, guys. I understand now. I guess it would have been just to much for MS to have a little note in the help for 5.0 saying that 3.0 syntax was a bit different :) :).
>
>So it's doing a tableupdate of all rows and not forcing. So I guess there's something about the table that's not allowing updates. That makes sense becuase I opened the view in a browse window and tried to change a field and it wouldn't let me do that either. At least I know I'm on the right track. Now, if I can just figure out why .... :)
>
>Another question for those of you that have a moment... I have a routine in my program that deletes all the old records of a table and reads in new information. Of course, it's a view too. And it's several thousand records. So what's happening here is that I use table exclusive and it takes a couple seconds to read that in. But the code continues immediately to try to execute even though it's not finished reading in all the records. Then I get an error message stating that the connection is busy. What I really need is for the execution of the code to pause until it's finished reading in all the records. I was thinking of putting some type of error trap in a loop so that whenever that error comes up I could put up a wait window or something informing the user that it's busy. That would solve the problem of making the code pause and letting the user know the computer is not locked up. What do you think of that? Would that be the best way to go about this?
>
>Thanks again for all your help.