A family of Microsoft relational database management systems designed for ease of use.
The performance of delete should not be ANY different here then your existing setup.
If you move your data to SQL server, and link the tables, then your sub form and editing as you have now should work and it will not require ANY changes to your code or even require ANY code at all.
When you have tables on SQL server, and you link to those tables, then your classic Access forms and even those sub forms should allow adding/editing/deleting JUST LIKE BEFORE you move that data to SQL server. Deleting a row will not behave any differnt to your users - and this includes performance - it should be instant.
For the most part your forms should work as before.
Additional issues to keep mind are:
When moving (upsizing) the data to SQL server, ALWAYS create a time stamp field.
When moving (upsizing) the data to SQL server, ALWAYS ensure the table has a primary key value.
If your tables have both the above, then your EXISTING forms + sub forms should work as before and should work without any changes to your code or forms. And the performance of a delete or general editing should not be ANY different of a user experiance then what you have now.
Best Regards
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada