In Access, we were able to have a combo box in a datasheet view when we had
a field referencing another table. It gave a friendlier approach to viewing
the table versus the numeric (for example) counterpart.

We migrated to SQL and all of those friendly combo boxes are gone. It is a
long shot to see if they are supported. Is this still possible using SQL
back-end with Access front-end?

Cheers,

Rich

Rich:

You can still do it in an Access project acting as a front end to an SQL
Server database. See the ProductID column in the OrderDetails table in the
sample NorthwindCS.adp project for an example. Its done in the same way as
in an Access .mdb database by setting the DisplayControl property to a Combo
Box in the Lookup tab of the columns properties sheet in table design view.

The real question, however, is should you? Most database developers tend to
favour not doing this in raw datasheet view but to stick with the actual
values of the foreign key column. Where a combo box should be used is in a
form, which is where data should be viewed and edited in a developed
application, not in datasheet view.

Ken Sheridan
Stafford, England

"RTL" wrote:

> In Access, we were able to have a combo box in a datasheet view when we had
> a field referencing another table. It gave a friendlier approach to viewing
> the table versus the numeric (for example) counterpart.
>
> We migrated to SQL and all of those friendly combo boxes are gone. It is a
> long shot to see if they are supported. Is this still possible using SQL
> back-end with Access front-end?
>
> Cheers,
>
> Rich
>
>
>