Controls are in tables rather than tables populating controls

[Chris Clement]

After migrating our Access database back-end to SQL Server and establishing
linked tables through ODBC, we have found that one of our forms on our
Access front-end are not acting correctly. This form is actually a subform
of another form. The subform consists of a drop-down box, a textbox, and a
check box. The values of these controls are assigned by a query. But now a
table is showing in the subform and the controls are in each of the columns
of each row. So instead of having one dropdown box, one textbox, and one
checkbox, I have a table with three columns and every row has each of the
controls. I have no idea what caused this or how to fix it. Strange. Any
help is greatly appreciated.

Using Access 2000 and SQL Server 2000.

 

[John Vinson]

But now a
table is showing in the subform and the controls are in each of the columns
of each row. So instead of having one dropdown box, one textbox, and one
checkbox, I have a table with three columns and every row has each of the
controls. I have no idea what caused this or how to fix it. Strange. Any
help is greatly appreciated.

Apparently the Subform is set to "Continous" view. This is normal
behavior for a continuous subform - you get rows of controls, one row
for each record in the form's recordsource.

If you want to see just a single record, change the Default View
property of the subform to "Single Form".