Kia:

The only problem with that is this:

Using INSERT INTO does not provide an easy way for you to access any default values you have specified for certain fields in your database.

For instance, take a look at the following code:

Select(lcMyTable)
Append Blank
Scatter Name loData Memo

Return loData

This effetively creates a "Data object" that you can pass across datasessions and through OLE channels. Plus, you have the added benefit of creating Virtual properties such as combining a person first and last name into simply name.

>Eric;
>It's not a good idea to use the APPEND BLANK with VFP. The best way to handle new record addition is to use INSERT INTO. This SQL command should resolve your problem.
>
>HTH
>
>Kia
>
>
>>I have a table that has a candidate index on a field named "project." Every once and a while though, the data entry associate accidently saves a blank project entry. Therefore, whenever he tries to add another record and APPEND BLANK kicks in, there is an immediate error that states the uniqueness of index is violated. All that makes perfect sense--however, after deleting the record from the form itself, it still keeps giving the same error. The data control options are set to "ignore deleted records" and the only way to fix this is to actually take exclusive control of the table and purge the record marked for deletion. Any suggestions on how to fix this? Thanks so much in advance. BTW, I'm using VFP 6.0