ENHANCEMENT REQUEST: Shared macros.dat files

General Macro Scheduler discussion

Moderators: JRL, Dorian (MJT support)

Post Reply

How important is this feature for future versions of Macro Scheduler?

Important, even if the size/efficiency of Macro Scheduler increases/degrades
1
100%
Somewhat important
0
No votes
I'm okay either way
0
No votes
Somewhat unimportant
0
No votes
Unimportant, even if the size/efficiency of Macro Scheduler remains unaffected
0
No votes
 
Total votes: 1

User avatar
Bob Hansen
Automation Wizard
Posts: 2475
Joined: Tue Sep 24, 2002 3:47 am
Location: Salem, New Hampshire, US
Contact:

ENHANCEMENT REQUEST: Shared macros.dat files

Post by Bob Hansen » Mon May 05, 2003 3:58 pm

Using 7.2.034

Enhancement Request:

Problem:
With Macro Scheduler installed on multiple machines it is practical to keep group folders on a network shared resource. But when new macros are added or deleted, these changes are not made on any other machine except the one where these modifications were done from. Modifications to the macro script itself is real time but the last date/time modified does not reflect changes made from another workstation until MS is restarted. This means that each workstation must now be updated by importing the additions and/or removing the deletions and/or quitting MS to update the Last Modified information..

Solution:
I know that the current structure has a file named "macros.dat" on each machine in the program folder for Macro Scheduler. This is great because it contains all of the scheduling information and allows different scheduling, controls, etc. for each workstation.

:idea: But would it be possible to split out the Groups Contents somehow to allow for shared macro folders; perhaps add a Refresh Button to the MS Control Panel to update the display with the latest additions/deletions, modification date/time?. Consider that the macros.dat file path could then be configured on each machine with the default to the current folder used now. The same thing could be done with a scheduling file. If this is pulled out, then it would be possible to share schedules vs. having to do each one individually. This sharing should be configured at the macro.scp level, not at the folder level. That would allow some scripts/schedules to be shared and others to be unique to the workstation.

Thanks for listening.
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!

User avatar
Bob Hansen
Automation Wizard
Posts: 2475
Joined: Tue Sep 24, 2002 3:47 am
Location: Salem, New Hampshire, US
Contact:

Post by Bob Hansen » Fri Jun 06, 2003 5:35 am

Added poll for other inputs....

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts