Runtime Error '3669'. Execution cancelled

[Shaleen Chugh]

Hi,

I have an MS Access 97 Frontend which had linked tables to MS SQL Server
2000. I have a linked table with 1.4 million rows with index on primary key.
When I exclude this table from the application works fine but when I include
it in my query, I get a Runtime Error '3669'. Execution cancelled and when I
try to debug it, it shows me the Table name where the application got stuck.

I am using the ODBC driver to connect to SQL Server.

Any leads would be greatly appreciated.

Thanks and Regards,

Shaleen Chugh

 

[Peter Hoyle]

This error seems to be usually related to a timeout problem
i.e. after so many seconds of running the query, it is intercepted by the
timeout, and you get the error message.

I'm not sure where to reset this with linked tables but there is a timeout
value for OLE/DDE
in Tools>Options>Advanced.

Cheers,
Peter

 

[Peter Hoyle]

Just another thought!

Can the query (or at least part of it) be run in SQL Server.
1.4 million rows is a bit much to be dragging over the network to process.

If you set up a view in SQL Server this can be linked
to Access in just the same way that you link actual tables.

I did this for some complex summary reports and they ran 30 times faster,

Regards,
Peter

 

[Peter Hoyle]

This error seems to be usually related to a timeout problem
i.e. after so many seconds of running the query, it is intercepted by the
timeout, and you get the error message.

In the properties sheet of the query you can reset the ODBC timeout period


For another approach: -

Can the query (or at least part of it) be run in SQL Server?
1.4 million rows is a bit much to be dragging over the network to process.

If you set up a 'View' in SQL Server this can be linked
to Access in just the same way that you link actual tables.

I did this for some complex summary reports and they ran 30 times faster,

Cheers,
Peter