Kevin,

Thanks. Guess I'll continue on with two banks of buttons. I don't like doing entry on grids but these folks have been using a system for years in which almost all their data entry is done in grids with very little validation. This is going to be a major transition for them so I'm picking my fights carefully. I definitely need to set a foreign key default value that can't readily be done from the SQL side. I don't really need any validation for the rest, so buttons with each grid should be a reasonable middle ground. At least I have some room on this screen.

By the way, I did change the AutoSetEnabled to false and that didn't make any difference.


>Linda,
>
>>I have 2 grids on a tab page in a business form. They are very simple and the users would like to enter data directly. I set the AllowUserToAddRows property to true. ReadOnly is false and Enabled is true. I made sure to create an instance of the related business objects. However, when I run the program, the grids are not enabled. I added code to specifically enable them in the Enter method but it didn't help. Currently, those tables are empty, but that shouldn't make a difference. What else do I need to do? Thanks.
>
>Try setting the grid's AutoSetEnabled property to false...
>
>That said, you typically don't want to enable the default Microsoft "Add New Row" funtionality because it simply adds a new record to the data source and completely bypasses the business object--which means it won't run any new "Hook" code, including setting default values.
>
>Best Regards,