Probably like user AERRORS() in Error method, check if this error number comes out then show a messagebox stating this form will be unavailable for the time being?

I am not sure what you are asking in the line above??? Anyway, you have to engineer the routine so the condition causing the issue won't occur (or is at least much less likely to happen). This would mean changing the 'other' program to stop using the table in an exclusive mode. If this is not possible, then just trapping the error and tell the users to come back later may the only (and totally unsatisfying) solution.

Kevin