>I'll have to do a search of the MS KB on this, Chris. Hopefully, since we're in 7.0 this will be something that's been fixed.

There will still be the problem with the @@IDENTITY value. It is not a bug, but a feature < g >. And it makes sense... if you ADD a record with an IDENTITY column, and a trigger is fired which ADDs a record in a table with an IDENTITY column, the @@IDENTITY value will be that of the second table. But this may not be a problem in your case.

>The only problem (so far) that I've had is that the VFP upsizing wizard (even in SP 4) wants the compatibility level set no higher than 6.5. So it's been into the Query Analyzer, set the compatibility level, upsize the table, then set it back.

After reading the Client/Server book, I avoided the Upsizing Wizard and used DTS (Data Transformation Services. I have had much better luck with that.