Sylvia,

In addition to Marc's points, there is a difference between adding a record while in Browse mode (live in VFP) and working on a form with buffering on. You may find that your triggers work when buffering is on. The triggers will only be called when you call TableUpdate(), giving users time to enter the necessary data.

HTH
Barbara

>Sylvia,
>
>Your question is not that basic!!! The problem is that you use databound controls (forms, grids, etc.), so when you append a blank record, well you append a blank record and your database triggers are fired. You might think of cloning your table and bind the forms to the clone, which is an approach I used, or sophisticate your trigger, or not use triggers at all ...
>
>HTH,
>
>Marc
>
>
>
>>This is a very basic question. I created some field level
>>and table level rules (things like this field can't be
>>blank). Then while browsing my table, I attempted to add
>>a new blank record. Obviously, when doing this, there
>>were blank fields, so I couldn't even add that record.
>>That wasn't my intent. I know there are going to be blank
>>fields for a new record because I haven't yet entered any
>>data. But, I want to prevent blank fields
>>(or whatever my legitimate rule is) after the user has
>>had a chance to actually add something. What am I missing
>>here?
>>
>>Sylvia