Leaving WL7 open and with the Data Manager > Scheduled Updates in focus is a far from optimal and not "automatic".
I suggest that we add switches for wealthlab7.exe to open the Data Manager to the Scheduled Update page so that the update action can be programmed easily in the Windows Task Scheduler:
Run: wealthlab7.exe /u /c
/u = update
/c = close when complete
I suggest that we add switches for wealthlab7.exe to open the Data Manager to the Scheduled Update page so that the update action can be programmed easily in the Windows Task Scheduler:
Run: wealthlab7.exe /u /c
/u = update
/c = close when complete
Rename
Actually I prefer the way how WL6 runs the "Auto Update".
WL6 runs the "Auto Update" without requiring either opening the Data Manager window or focusing the Scheduled Update tab.
Because I may be using WL7 at the time when the "Auto Update" is scheduled, the Task Scheduler method may not work well.
WL6 "Auto Update" works really well. All I have to do is to leave WL6 window open, then WL6 opens the Data Manager window by itself and starts the update. Even if I'm using WL6, the Data Manager window opens up automatically and it starts the update. WL6 just works well.
WL6 runs the "Auto Update" without requiring either opening the Data Manager window or focusing the Scheduled Update tab.
Because I may be using WL7 at the time when the "Auto Update" is scheduled, the Task Scheduler method may not work well.
WL6 "Auto Update" works really well. All I have to do is to leave WL6 window open, then WL6 opens the Data Manager window by itself and starts the update. Even if I'm using WL6, the Data Manager window opens up automatically and it starts the update. WL6 just works well.
This feature request is about bringing more flexibility to the update process by calling the executable with various parameters. IMHO it may open up for doing more tasks for server side operation in the future - say starting Strategy Monitor or running an optimization, who knows?
Also, Wealth-Lab 7 can run multiple instances so another instance won't interfere with your WL7 usage.
Also, Wealth-Lab 7 can run multiple instances so another instance won't interfere with your WL7 usage.
QUOTE:I didn't know about it. In which case, I prefer Task Scheduler way. Thanks!
Wealth-Lab 7 can run multiple instances so another instance won't interfere with your WL7 usage.
Activating this for Build 16 development.
Your Response
Post
Edit Post
Login is required