Do we need all the extra stuff in pre-made macros?

[Monterey_Manzer]

Hi,



I am developing a series of forms and corresponding tables used to track issues of various sorts. When one of these issues is resolved we delete the record on the Access table. However, it is desirable that we have some sort of record keeping to track those issues we have encountered. I simply added a Delete Record button whose macro is a group of ExportWithFormatting (The table as Excel workbook) along with RunMenuCommand.DeleteRecord.

I noticed that when I go through the "wizard" steps for setting up a Delete Record button, there are quite a bit more commands than just RunMenuCommand.Delete Record. I get an OnError command, GoToControl, ClearMacroError, and 4 If, Then commands which include a Delete Record and Undo Record command along with some Macro Error and Message Box commands. I am sure anyone who goes through the steps of setting up a Delete Record button on a form in Access 2010 will see the same list of macro commands

My question is do we need this stuff? What does it do for us? I like just having an Export and Delete record command grouped together as it is easier for my novice brain to comprehend but should I include all these steps instead?

[Robeen]

You may not want [or need] all those extra features - but they are in there because in the course of common Add, Modify, Delete activities in most Database applications, those are the things you might want/need to handle.
Access is just trying to make it easier for you [should you want to use those functions].
If you don't want them and they really BUG you [ ] - get rid of them.
When data is critical, there are all these programming 'checks & balances' . . .