Wow, nice, thanks for the spreadsheet, sensij!
To answer the specific original question, there's this MOMO command sensij mentioned, and also under the "I/O Unit Commands," we have: Move Numeric Table to I/O Unit.
Both of these commands assume all the points are on the same I/O unit.
I would agree w/the Pointer Table solution, as Ben figured I would. The Pointer Table method does NOT assume all the points are on the same I/O Unit, nor does it get messed up if you were to move points around (to a different spot on the rack, or do a different rack completely). Maddosc also mentioned changing the point names, which is a good idea since they could be much more descriptive/helpful than Output_0 etc.
I'd also like to second the plug for the user manual section Ben mentioned which breaks the Pointer Table technique nicely:
AFTER in Action/Condition Blocks:
AFTER in OptoScript:
Good question & suggestions, keep 'em coming!