I am not sure.  I would have to play with this first.  We do not use the DX grid so I am not as familiar with it off the top of my head.  Sorry

Thanks for the example.  I replaced the example's grid with one from DX and it worked great.

One question.  As you're probably aware the DX grid via built in context menu allows the user to manage which fields are visible.   How would a person disallow hidding a required field.  Trying to save a record where there's a broken rule with the offended column hidden would be difficult at best for most users.

I haven't tried to figure this out yet myself.  Thought I'd ask in case you may already have a quick answer.  If not let's see what we can turn up  

No problem.

Thanks for the extremely quick response.  I will check this out ASAP. 

The business rules will be respected within a grid when using a BusinessBindingSOurce.  Attached is a sample that will be included in the next update.  This sample shows how to use a BusinessBindingSOurce with a grid.  If you create a new record and try to save, you will see the broken rules show up within the grid.

I'm a trial user.  I'm needing to migrated a commerial Access Time and Billing application (TimeWerkes) to .net/sql.  I'm wondering if there are any examples of data entry via a grid only.  In my app 95% of the data entry is done via a grid (Janus).

I probably have too many questions to list, but maybe an example would clear things up for me.

The scenario goes:

Create Employee Timesheet  - Master record

Add many timesheet details for the current pay/billing period.  Each record that goes into the grid needs required fields checking, default values set (dependant on project setup) etc, etc.

One of my cusotmers averages between 650 and 800 timesheets per period, so that means tons of data entry via the grid.