>I suspected that was the case, but didn't have the experience to back it up. Now I know why the View Designer defaults that way... :-) So, afterwards, if you want to see it, you just do a REQUERY()?

Well, it's a bit more complicated than that. In SQL Server you can SELECT @@INDENTIY. That returns the last identity value created on that connection. I usually just do that and then REPLACE the PK field in the view with that value (no harm done since that field isn't updatable, anyway). If you just REQUERY() it's going to use the parameters of the view (if any) to limit the records returned. The record you added might not even come back.

>P.S.: going to Waltham tonight? (for those not on the mailing list, Ted Roche is speaking on Project Hooks at MS at 7:00.)

Unfortunately, I can't make it. I'm leaving on a two week vacation tomorrow and I have a million things to do.