I'm thinking about what I'd need to actually move off of access type forms to silverlight, in terms of a datagrid.  It could be this is possible only with silverlight fully trusted or "out of the (sand)box" (which is fine with me), or wpf (--though it seems silverlight is the end goal according to MS).   fwiw, this is my reaction--don't know if it's useful or maybe I have a fundamental misconception of wpf/silverlight tools: 

First, a small point, it would help to have a "binding navigator" option with CRUD operation easily available for all views (including card view);  for example:
http://weblogs.thinktecture.com/cnagel/2010/08/bindingnavigator-for-wpf-part-1---creating.html

On an ideal datagrid: I'd want a control that easily allows one to create master-detail (ContainingForm with contained subforms) with crud buttons and nav. bars on both form and subform, and one that easily "understands" the relation between form and subform.  I mean something like Microsoft access has in its forms, or I think to some extent in winforms, but for silverlight (or wpf).   I'd think one could use a datagrid for that by first having a big single container card view (one-record-at-a-time view, fields vertically arranged), with a navigation bar--this would be for the master table, for ex. customers, as the master form or master grid.  Then drop another datagrid into it for a fully contained "subform" (a child/details table, e.g. Orders, probably horizontally arranged fields), and perhaps a second subform or contained datagrid (for a second child table, or grandchild ("orderdetails") linked to the selected child).  But I don't know if that's easy with the tools now and  I don't know how comparable to access form templates ("split form"; "columnar," each with subforms etc); the datagrids I see available don't seem to have that.  The peculiar advantage of a datagrid in ease of use is large, because one is not creating a whole form layout composed of unrelated elements with their own custom formats and individual positioning etc, but relying on a simple auto-organization (i.e. a row of fields, but the fields can also be in vertical layout or two column wrap organization etc.).   --Looking for as simple and automatic an experience as possible, "churn out" forms based on dropping a couple of related tables for crud operations, and that require only minor customization.  The goal is not to have the whole wpf/blend design experience -- I don't need or want it, too much time, too many options etc.  One wants the wpf/silverlight tools support (and future), but with a simple lob autoform generator for standard crud operations.   That's my general impression, perhaps as I learn more about wpf/silverlight I'll have a better handle on the best combination of rad tools (what I don't want to do is spend a lot of time on ui). 

as far as I can see, the closest view in xceed to what I use most often seems to be the master/detail (in the wpf grid), but there I didn't see master as card view container with one or more detail tables as contained elements.  Master-detail view in xceed seems (in the most basic format) to be like a tree explorer view (like table/subtable in access datasheet view).  I assume one could do two or three grids separately (e.g. one card master grid and two child table view grids) and link them up, and then add a navigation bar and crud buttons and synchronization logic etc., or perhaps even do it in a customized template, but offhand that's not as autogenerated/automatic as I'd like.     Thanks.