DataSheet Defalt View

[scott]

I've never used the "DataSheet" default view type in a subform. I was
looking at an example database that used the "DataSheet" type in all of
their subforms.

What I can't seem to figure out is how the id field gets hiden. For example,
if a table has 2 fields called customerID and customerName and a subform has
both felds represented using text boxes and the default view is datasheet
type, when I view the form, the customerID textbox control and it's
connected label don't et displayed.

I look at the proprties to check nthe visible property and both controls are
set to be visible.

Is access smart enough to know a control is a primary key and hide it?

Any schooling on the datasheet view would be appreciated.

thanks

 

[John W. Vinson]

I've never used the "DataSheet" default view type in a subform. I was
looking at an example database that used the "DataSheet" type in all of
their subforms.

I've never understood why.

What I can't seem to figure out is how the id field gets hiden. For example,
if a table has 2 fields called customerID and customerName and a subform has
both felds represented using text boxes and the default view is datasheet
type, when I view the form, the customerID textbox control and it's
connected label don't et displayed.

I look at the proprties to check nthe visible property and both controls are
set to be visible.

Is access smart enough to know a control is a primary key and hide it?

No. You can set its Width to zero, or just not include it in the subform's
recordsource.

Any schooling on the datasheet view would be appreciated.

The only benefit I've ever seen to datasheets - and it's a very questionable
benefit, in my experience - is that users can resize columns or rows by
grabbing the line between them with the cursor.

I just use Continuous Forms instead. They can be made to look very like a
datasheet but allow more flexibility in controls, and more freedom for the
developer (and somewhat less for the user).

John W. Vinson [MVP]