J
John Piotrowski
I'm having a problem with a database that I just can't figure out. My
tables are all linked SQL Server tables. I have a form with employee
information and a subform that contains related records.
On the form I have a button for deleting the employee and it calls 2
queries. The first removes all the related records and the second removes
the employee record.
The problem I'm having is that the query that deletes the employee record
times out and won't delete the record. The data was imported from an old
DOS program. I can add a new employee and related records and then go back
and delete the employee. But if I try to delete any of the existing records
that were imported, I get the timeout error.
I can go into query design, and run the query from there and delete employee
records. In the form I tried using docmd.openquery and also docmd.runsql
with the same results.
I thought it might be a record locking problem but then the problem should
be consistant with all records not just the imported ones.
I've written other databases that work similar to this without a problem.
Any ideas?
John
tables are all linked SQL Server tables. I have a form with employee
information and a subform that contains related records.
On the form I have a button for deleting the employee and it calls 2
queries. The first removes all the related records and the second removes
the employee record.
The problem I'm having is that the query that deletes the employee record
times out and won't delete the record. The data was imported from an old
DOS program. I can add a new employee and related records and then go back
and delete the employee. But if I try to delete any of the existing records
that were imported, I get the timeout error.
I can go into query design, and run the query from there and delete employee
records. In the form I tried using docmd.openquery and also docmd.runsql
with the same results.
I thought it might be a record locking problem but then the problem should
be consistant with all records not just the imported ones.
I've written other databases that work similar to this without a problem.
Any ideas?
John