Macros for offices coming from Lotus Approach: a library of named macros, macros that run on their own, a branch, a loop over the records found, and eight new things a button can do:
- Named macros: a list of steps kept under a name on each table, written once on the new Macros screen and run from any button with the "Run a macro" step. A macro that would run itself, directly or through others, is refused when it is saved, with the chain spelled out
- A form can run a macro when it opens, and another when a new record starts — "set Status to New and stamp today's date" on every new card
- Run a macro if a test holds: a yes-or-no test about the record picks which of two named macros runs
- Run a macro on every record found: it asks first with the count, then works through the records one at a time, saving each as it goes. A guard inside the macro passes a record over; a record that refuses its change stops the run there and says how far it got; Cancel stops it after the record in hand; and pressing again offers to carry on with the records not done yet
- Set a field on every record found: the loop Approach users wrote most, without a loop. It asks first with the count, then saves every record at once, or none if one refuses
- Seven more steps: save the record, show the related records through a relationship, print a report, show a message worked out from the record, put the cursor in a field, open a saved query, and duplicate the record
- Phone numbers written as tel: links open in your phone or calling app, from a field or a button
- A formula can add days to a date: [Due] + 14
- A field that a button's or a macro's test reads can no longer be deleted, or changed to a type the test cannot use, until the test is changed: removing the test quietly would change what every later press writes
- Opening a database in 1.2 upgrades its file, and earlier versions cannot open it afterwards, so move every computer in an office to 1.2 together
