Keith ----

>>No problem, but your concern about having inadvertently blank record is not well grounded just because, normally, app relies on INSERT-SQL adding knew records.
>
>Your assuming *everyone* uses INSERT-SQL. There are still a lot of us "old timers" that still find use for APPEND BLANK (and spare me the "INSERT over APPEND BLANK" platitudes, I know them all.< bg >). Thanks again.

It used to be that APPEND BLANK was just clunky compared to INSERT INTO...now, with Primary keys and other concerns, it doesn't make sense not to use INSERT INTO. Its like still using SHOW GETS or something in VFP. Sure you can do it, but, jeez.

I have to back up Ed on this one: If you use a Primary key and get an error because of the restrictiveness of how VFP manages it, well....GOOD! Every DBMS I know of craps and dies to some degree or another with a Primary key violation. In that sense, a primary key should not be anymore "troublesome" than any other index type becuase if it is giving you an error - You-Are-Doing- Something-Wrong.