Panorama keeps track of Undo separately for different contexts. Each database has a it’s own Undo “stack” (history of actions that can be undone), and when editing graphics, each form has it’s own Undo stack. Each procedure also has it’s own separate Undo stack.
When you write program code yourself, it normally isn’t undo-able. However, you can easily write your code so that it can be undone. See startdatabasechange to learn how.
|10.0||Updated||Carried over from Panorama 6.0, but now includes multi-level undo for virtually all operations.|