• The challenge in doing that is to know that the subform controls are displaying "=deleted" - it's not something I've ever attempted. If you can do that then you could hide the subform control until it has been populated. But that text popping up doesn't trigger an event as far as I know, so there's the problem. You could certainly try putting a bit a code behind the "Before Del Confirm", "On Delete", and "After Del Confirm" to display a simple text box message, but I don't think it will work. I presume you have solved the situation where multiple users were sharing the same database and clobbering the temporary table.

    Chris makes an excellent point - with SQL Server tables you want to make sure that the have a default value defined for bit fields, or you will have all sorts of trouble. Another thing you should also do is to give each linked table a TimeStamp field. Access is much happier when you do that - if you don't you tend to get ODBC error messages that another user has edited the record, and your changes cannot be saved.

    Wendell

    Wendell
    Colorful Colorado
    You can't see the view if you don't climb the mountain!