LInked table returns #Name? on long scroll

[SimonSellick]

Hi,

I'm attempting to migrate a large table from Access 97 to SQL Server and link to it in Access.

All appears to be OK until I open the linked table and do cntl-end to get to the last record. I then get an unspecified ODBC error (ODBC--CallFailed) and all the fields display #Name? However, it does find the correct number of records.

I thought that I was on the right track with memo fields containing control characters, but apprently not as removing them doesn't fix the problem. The table has a primary key (if I remove it the problem goes away but the recordset is then not updateable which is no good for this app).

The front-end is Access 97, back end is SQL Server 2000; there is no security set in Access and I'm using integrated Windows security with SQL Server (trusted connection). The table is large (340K rows and 4KB / row) but the message appears after only about 5 seconds, so I don't think that it is timing out.

Any help appreciated. Although I've seen #Name? before within Access, I haven't come across it in a simple linked table.

 

[lameid]

From the far reaches of my mind... I think there is a registry setting that sets how many rows / data can be transfered via ODBC in Access.

 

[SimonSellick]

Thanks lameid, but I think that I've found the cause - column names containing spaces. If I alter them all to underscores, the problem disappears.

 

[lameid]

That's odd, both products support spaces in field names. Anyways, it is working and that is the goal.