A program to recognize and reward our most engaged community members
We are in the process of migrating to Windows 10 Enterprise and I am having issues with Monarch Version 9.0. I was wondering if anyone else has had this issue? Also, I was wondering if this version works with WIndows 10?
Hi Darrell,
What sort of problems are you seeing?
V9 will not run at all?
Or certain things do not seem to be working?
I can't answer for WIn 10 - I have been avoiding it successfully so far!
Have you re-installed after the Windows upgrade? If not that might be worth a try - preferably on a test machine if someone has one available.
Grant
Hi Darrell, What sort of problems are you seeing? V9 will not run at all? Or certain things do not seem to be working? I can't answer for WIn 10 - I have been avoiding it successfully so far! Have you re-installed after the Windows upgrade? If not that might be worth a try - preferably on a test machine if someone has one available. Grant
I checked the computer this morning and the user said it worked now not sure what happened over the weekend but it fixed itself.
Good news.
And yeah, who knows what the computers get up to amongst themselves when left to play over a weekend?!
Good news. And yeah, who knows what the computers get up to amongst themselves when left to play over a weekend?!
Lol
Get Outlook for Android<https://aka.ms/ghei36>
We are running Monarch 10.5 Pro at work. I was just migrated over from Windows 7 to Windows 10 recently and Monarch 10.5 Pro does work. The only issue I have is I cannot run any scripts that call Monarch. If I open Monarch first, no problem. It is only when I try to run everything from a script that I have issue. I had no problem under Windows 7.
In Windows 7 I would start Monarch via the script with the following script:
Sub OpenMonarch()
Call Shell(Environ$("COMSPEC") & " /c G:\Accounting\PRM_ACTG\Monarch\BatchFiles\Monarch.bat ", vbHide)
Application.Wait (Now + TimeValue("0:00:10"))
End Sub
that would then call the batch file that started Monarch:
\\Lnk-smb03.tagtmi.com\software\Monarch\Program\Monarch.exe
I run approx. 50 scripts that use Monarch every morning as a scheduled task. So manually starting Monarch each time isn't really feasible.
Are there any gurus out there that can help me?
Thanks in advance for any help.
Ralph
We are running Monarch 10.5 Pro at work. I was just migrated over from Windows 7 to Windows 10 recently and Monarch 10.5 Pro does work. The only issue I have is I cannot run any scripts that call Monarch. If I open Monarch first, no problem. It is only when I try to run everything from a script that I have issue. I had no problem under Windows 7. In Windows 7 I would start Monarch via the script with the following script: Sub OpenMonarch() Call Shell(Environ$("COMSPEC") & " /c G:\Accounting\PRM_ACTG\Monarch\BatchFiles\Monarch.bat ", vbHide) Application.Wait (Now + TimeValue("0:00:10"))End Sub that would then call the batch file that started Monarch: \\Lnk-smb03.tagtmi.com\software\Monarch\Program\Monarch.exe I run approx. 50 scripts that use Monarch every morning as a scheduled task. So manually starting Monarch each time isn't really feasible. Are there any gurus out there that can help me? Thanks in advance for any help. Ralph
Hi Ralph -
Without getting too technical, have you tried changing your script from using batch files to instead use Monarch 10's COM object?
Hi Ralph -Without getting too technical, have you tried changing your script from using batch files to instead use Monarch 10's COM object?
I am not up-t0-date with writing batch files. I have always programed Monarch with Excel like Kruncher.
You got a way to write a batch program to start Monarch with Windows 10 like I did with Windows 7?
I am not up-t0-date with writing batch files. I have always programed Monarch with Excel like Kruncher. You got a way to write a batch program to start Monarch with Windows 10 like I did with Windows 7? Ralph
The script you supplied above is shelling out to the OS and running a batch file.
You would need to program the steps that are in the batch file into VB/VBA instead - eliminating the batch file altogether.
