>>Can it be memory related? Bad SIM?
>
>No, we checked that. I got the operand error
>figured out, but I am still having an ODBC
>problem. The TableUpdate() function is returning
>False, but is writing the changes to the back end
>anyway. It only does this on certain machines. I'm
>able to reproduce this error on a 486DX66, a
>486DX33 (both HP) and now on a 486DX100 (Blue
>Star) so I'm ruling out hardware now. I've checked
>the network connections as well.
>
>Thanks for the reply,
>Scot.

An Update, FYI;

It turned out to be a different version of the ODBC files. I noticed that the ODBC administrator was different between the working machines and the others. I think either: 1) the version of the ODBC files that are installed when you install VFP are different than the files packaged by the Setup Wizard or 2) the ODBC files packaged with VFP and the Setup Wizard do not work with SQL Server 6.0 (as the working machines also had other development platforms with ODBC installed on them at one time i.e. VB, etc). When I looked at the files, they had a different date (by 2 days, go figure) and different versions. This was probably documented somewhere, if only I had thought of it.....:)

Thanks to those who responded,
Scot.