Sage 100

Restore RPT from backup???  Run the mascrcw.exe utility?

Only happens on one machine.  Pretty sure this is something networky...

Restore RPT from backup???  Run the mascrcw.exe utility?

Are scripts restricted on the workstation?

I'm going to have to look at the options again tomorrow.  I toggled the Debugging option but didn't check re scripting, period.  It's all setup differently on Win 11, so I'll have to look more thoroughly.  I hate you, Microsoft programmers.  (And I REALLY hate you because of how many times I have to click on More option when I right click on a file now. )

Are scripts restricted on the workstation?

This link might be worth a look.

https://www.supportyourtech.com/tech/how-to-enable-running-scripts-in-windows-11-a-step-by-step-guide/

I'm going to have to look at the options again tomorrow.  I toggled the Debugging option but didn't check re scripting, period.  It's all setup differently on Win 11, so I'll have to look more thoroughly.  I hate you, Microsoft programmers.  (And I REALLY hate you because of how many times I have to click on More option when I right click on a file now. )

Are scripts restricted on the workstation?

Funny, @Doug Higgs - I had just Googled that from a different angle.  Unfortunately, even setting it to unrestricted made no difference.

I'm going to open a case with Sage.

This link might be worth a look.

https://www.supportyourtech.com/tech/how-to-enable-running-scripts-in-windows-11-a-step-by-step-guide/

I'm going to have to look at the options again tomorrow.  I toggled the Debugging option but didn't check re scripting, period.  It's all setup differently on Win 11, so I'll have to look more thoroughly.  I hate you, Microsoft programmers.  (And I REALLY hate you because of how many times I have to click on More option when I right click on a file now. )

Are scripts restricted on the workstation?

SO because the report was "modified" (had prompts), Sage wouldn't help and just threw up their hands.  The client then reported the dreaded "printing screen flashes and disappears, then when we run it the second time it's OK" so I decided to put them back to 32 bit (and then take off the Auto update of the DTR - this really pisses me off).  Once I put it back to 32 bit I had to uninstall the 32 and 64 bit Crystal runtimes and reinstalled ONLY the 32 bit, and the report with its prompts ran just fine.

SOOOOOOO chalk up another 64 bit issue.  I was really a champion of 64 bit at first, but now I'm totally over it, and VERY pissed off about the 32 bit DTR issue. I am one big ball of GRRRRRR this morning when it comes to Sage.

Funny, @Doug Higgs - I had just Googled that from a different angle.  Unfortunately, even setting it to unrestricted made no difference.

I'm going to open a case with Sage.

This link might be worth a look.

https://www.supportyourtech.com/tech/how-to-enable-running-scripts-in-windows-11-a-step-by-step-guide/

I'm going to have to look at the options again tomorrow.  I toggled the Debugging option but didn't check re scripting, period.  It's all setup differently on Win 11, so I'll have to look more thoroughly.  I hate you, Microsoft programmers.  (And I REALLY hate you because of how many times I have to click on More option when I right click on a file now. )

Are scripts restricted on the workstation?

SO because the report was "modified" (had prompts), Sage wouldn't help and just threw up their hands.  The client then reported the dreaded "printing screen flashes and disappears, then when we run it the second time it's OK" so I decided to put them back to 32 bit (and then take off the Auto update of the DTR - this really pisses me off).  Once I put it back to 32 bit I had to uninstall the 32 and 64 bit Crystal runtimes and reinstalled ONLY the 32 bit, and the report with its prompts ran just fine.

SOOOOOOO chalk up another 64 bit issue.  I was really a champion of 64 bit at first, but now I'm totally over it, and VERY pissed off about the 32 bit DTR issue. I am one big ball of GRRRRRR this morning when it comes to Sage.

Funny, @Doug Higgs - I had just Googled that from a different angle.  Unfortunately, even setting it to unrestricted made no difference.

I'm going to open a case with Sage.

This link might be worth a look.

https://www.supportyourtech.com/tech/how-to-enable-running-scripts-in-windows-11-a-step-by-step-guide/

I'm going to have to look at the options again tomorrow.  I toggled the Debugging option but didn't check re scripting, period.  It's all setup differently on Win 11, so I'll have to look more thoroughly.  I hate you, Microsoft programmers.  (And I REALLY hate you because of how many times I have to click on More option when I right click on a file now. )

Are scripts restricted on the workstation?

Did you report your findings back to an intelligent person at Sage?  If not, please email them to Scott Brady for further review.  I find him helpful.  Need to turn up the heat to get these issues resolved,  Especially since the official fix to the DTR is to run in 64bit mode

SO because the report was "modified" (had prompts), Sage wouldn't help and just threw up their hands.  The client then reported the dreaded "printing screen flashes and disappears, then when we run it the second time it's OK" so I decided to put them back to 32 bit (and then take off the Auto update of the DTR - this really pisses me off).  Once I put it back to 32 bit I had to uninstall the 32 and 64 bit Crystal runtimes and reinstalled ONLY the 32 bit, and the report with its prompts ran just fine.

SOOOOOOO chalk up another 64 bit issue.  I was really a champion of 64 bit at first, but now I'm totally over it, and VERY pissed off about the 32 bit DTR issue. I am one big ball of GRRRRRR this morning when it comes to Sage.

Funny, @Doug Higgs - I had just Googled that from a different angle.  Unfortunately, even setting it to unrestricted made no difference.

I'm going to open a case with Sage.

This link might be worth a look.

https://www.supportyourtech.com/tech/how-to-enable-running-scripts-in-windows-11-a-step-by-step-guide/

I'm going to have to look at the options again tomorrow.  I toggled the Debugging option but didn't check re scripting, period.  It's all setup differently on Win 11, so I'll have to look more thoroughly.  I hate you, Microsoft programmers.  (And I REALLY hate you because of how many times I have to click on More option when I right click on a file now. )

Are scripts restricted on the workstation?

I replied back to the original case, and I also followed up on my other case re the 64 bit printing screens disappearing to let them know a brand new upgrade was having that issue.

Then I went back to bed and curled up in a fetal position.

Did you report your findings back to an intelligent person at Sage?  If not, please email them to Scott Brady for further review.  I find him helpful.  Need to turn up the heat to get these issues resolved,  Especially since the official fix to the DTR is to run in 64bit mode

SO because the report was "modified" (had prompts), Sage wouldn't help and just threw up their hands.  The client then reported the dreaded "printing screen flashes and disappears, then when we run it the second time it's OK" so I decided to put them back to 32 bit (and then take off the Auto update of the DTR - this really pisses me off).  Once I put it back to 32 bit I had to uninstall the 32 and 64 bit Crystal runtimes and reinstalled ONLY the 32 bit, and the report with its prompts ran just fine.

SOOOOOOO chalk up another 64 bit issue.  I was really a champion of 64 bit at first, but now I'm totally over it, and VERY pissed off about the 32 bit DTR issue. I am one big ball of GRRRRRR this morning when it comes to Sage.

Funny, @Doug Higgs - I had just Googled that from a different angle.  Unfortunately, even setting it to unrestricted made no difference.

I'm going to open a case with Sage.

This link might be worth a look.

https://www.supportyourtech.com/tech/how-to-enable-running-scripts-in-windows-11-a-step-by-step-guide/

I'm going to have to look at the options again tomorrow.  I toggled the Debugging option but didn't check re scripting, period.  It's all setup differently on Win 11, so I'll have to look more thoroughly.  I hate you, Microsoft programmers.  (And I REALLY hate you because of how many times I have to click on More option when I right click on a file now. )

Are scripts restricted on the workstation?

With class of wine nearby?

I replied back to the original case, and I also followed up on my other case re the 64 bit printing screens disappearing to let them know a brand new upgrade was having that issue.

Then I went back to bed and curled up in a fetal position.

Did you report your findings back to an intelligent person at Sage?  If not, please email them to Scott Brady for further review.  I find him helpful.  Need to turn up the heat to get these issues resolved,  Especially since the official fix to the DTR is to run in 64bit mode

SO because the report was "modified" (had prompts), Sage wouldn't help and just threw up their hands.  The client then reported the dreaded "printing screen flashes and disappears, then when we run it the second time it's OK" so I decided to put them back to 32 bit (and then take off the Auto update of the DTR - this really pisses me off).  Once I put it back to 32 bit I had to uninstall the 32 and 64 bit Crystal runtimes and reinstalled ONLY the 32 bit, and the report with its prompts ran just fine.

SOOOOOOO chalk up another 64 bit issue.  I was really a champion of 64 bit at first, but now I'm totally over it, and VERY pissed off about the 32 bit DTR issue. I am one big ball of GRRRRRR this morning when it comes to Sage.

Funny, @Doug Higgs - I had just Googled that from a different angle.  Unfortunately, even setting it to unrestricted made no difference.

I'm going to open a case with Sage.

This link might be worth a look.

https://www.supportyourtech.com/tech/how-to-enable-running-scripts-in-windows-11-a-step-by-step-guide/

I'm going to have to look at the options again tomorrow.  I toggled the Debugging option but didn't check re scripting, period.  It's all setup differently on Win 11, so I'll have to look more thoroughly.  I hate you, Microsoft programmers.  (And I REALLY hate you because of how many times I have to click on More option when I right click on a file now. )

Are scripts restricted on the workstation?