Sage 100

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

As Alnoor says, grid loading, and any kind of access where batches are enabled (also a grid) is quite slow on Advanced in V2019 - 2021.  (We didn't have this issue in 2018 – it only started with v2019).  It does take between 6 and 10 seconds to load batches, when you're in a Data Entry screen where batches have been enabled. When you're trying to print anything where a batch has been enabled, folks end up clicking on a menu item multiple times, thinking their first "click" didn't register.  Eventually, the batch screen comes up, but then so do 3 or 4 others where the client clicked the menu item again.  Double clicking on an Invoice in AR used to take no time at all to load, and now you can count to at least 6 before that invoice comes to the screen.

Sage thought they had narrowed the problem down to the client's Remote RDP access, but turns out they didn't clear their redirected printers when they tested.  (And re-directed printers is also an issue on Advanced – we've solved that by using TS Print however, and that works well.)  So – it wasn't the remote app after all.  And – sadly - we did just receive a note from Nathan Shaw, after he had tested the client data for a little over a week.  And the note said: "We can duplicate the problem, but we've discussed the issue with Engineering and there is nothing that can be done.  So, there is nothing we can do to speed up the system." 

That's it.  That's all we have – as I mentioned, our IT Team is still attempting to see if the problem is with the Terminal Server or not – but something did indeed change with V2019.

Sue Bennett | President

Bennett/Porter & Associates, Inc.

P. 503 620 3484 | F. 503 620 2765

12559 SW 69th Ave | Portland, OR  97223

Email address | www.benpor.com

Bennett/Porter Blog | facebook | twitter

The information in this email and any attachments is considered confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

As Alnoor says, grid loading, and any kind of access where batches are enabled (also a grid) is quite slow on Advanced in V2019 - 2021.  (We didn't have this issue in 2018 – it only started with v2019).  It does take between 6 and 10 seconds to load batches, when you're in a Data Entry screen where batches have been enabled. When you're trying to print anything where a batch has been enabled, folks end up clicking on a menu item multiple times, thinking their first "click" didn't register.  Eventually, the batch screen comes up, but then so do 3 or 4 others where the client clicked the menu item again.  Double clicking on an Invoice in AR used to take no time at all to load, and now you can count to at least 6 before that invoice comes to the screen.

Sage thought they had narrowed the problem down to the client's Remote RDP access, but turns out they didn't clear their redirected printers when they tested.  (And re-directed printers is also an issue on Advanced – we've solved that by using TS Print however, and that works well.)  So – it wasn't the remote app after all.  And – sadly - we did just receive a note from Nathan Shaw, after he had tested the client data for a little over a week.  And the note said: "We can duplicate the problem, but we've discussed the issue with Engineering and there is nothing that can be done.  So, there is nothing we can do to speed up the system." 

That's it.  That's all we have – as I mentioned, our IT Team is still attempting to see if the problem is with the Terminal Server or not – but something did indeed change with V2019.

Sue Bennett | President

Bennett/Porter & Associates, Inc.

P. 503 620 3484 | F. 503 620 2765

12559 SW 69th Ave | Portland, OR  97223

Email address | www.benpor.com

Bennett/Porter Blog | facebook | twitter

The information in this email and any attachments is considered confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

As Alnoor says, grid loading, and any kind of access where batches are enabled (also a grid) is quite slow on Advanced in V2019 - 2021.  (We didn't have this issue in 2018 – it only started with v2019).  It does take between 6 and 10 seconds to load batches, when you're in a Data Entry screen where batches have been enabled. When you're trying to print anything where a batch has been enabled, folks end up clicking on a menu item multiple times, thinking their first "click" didn't register.  Eventually, the batch screen comes up, but then so do 3 or 4 others where the client clicked the menu item again.  Double clicking on an Invoice in AR used to take no time at all to load, and now you can count to at least 6 before that invoice comes to the screen.

Sage thought they had narrowed the problem down to the client's Remote RDP access, but turns out they didn't clear their redirected printers when they tested.  (And re-directed printers is also an issue on Advanced – we've solved that by using TS Print however, and that works well.)  So – it wasn't the remote app after all.  And – sadly - we did just receive a note from Nathan Shaw, after he had tested the client data for a little over a week.  And the note said: "We can duplicate the problem, but we've discussed the issue with Engineering and there is nothing that can be done.  So, there is nothing we can do to speed up the system." 

That's it.  That's all we have – as I mentioned, our IT Team is still attempting to see if the problem is with the Terminal Server or not – but something did indeed change with V2019.

Sue Bennett | President

Bennett/Porter & Associates, Inc.

P. 503 620 3484 | F. 503 620 2765

12559 SW 69th Ave | Portland, OR  97223

Email address | www.benpor.com

Bennett/Porter Blog | facebook | twitter

The information in this email and any attachments is considered confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

As Alnoor says, grid loading, and any kind of access where batches are enabled (also a grid) is quite slow on Advanced in V2019 - 2021.  (We didn't have this issue in 2018 – it only started with v2019).  It does take between 6 and 10 seconds to load batches, when you're in a Data Entry screen where batches have been enabled. When you're trying to print anything where a batch has been enabled, folks end up clicking on a menu item multiple times, thinking their first "click" didn't register.  Eventually, the batch screen comes up, but then so do 3 or 4 others where the client clicked the menu item again.  Double clicking on an Invoice in AR used to take no time at all to load, and now you can count to at least 6 before that invoice comes to the screen.

Sage thought they had narrowed the problem down to the client's Remote RDP access, but turns out they didn't clear their redirected printers when they tested.  (And re-directed printers is also an issue on Advanced – we've solved that by using TS Print however, and that works well.)  So – it wasn't the remote app after all.  And – sadly - we did just receive a note from Nathan Shaw, after he had tested the client data for a little over a week.  And the note said: "We can duplicate the problem, but we've discussed the issue with Engineering and there is nothing that can be done.  So, there is nothing we can do to speed up the system." 

That's it.  That's all we have – as I mentioned, our IT Team is still attempting to see if the problem is with the Terminal Server or not – but something did indeed change with V2019.

Sue Bennett | President

Bennett/Porter & Associates, Inc.

P. 503 620 3484 | F. 503 620 2765

12559 SW 69th Ave | Portland, OR  97223

Email address | www.benpor.com

Bennett/Porter Blog | facebook | twitter

The information in this email and any attachments is considered confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

As Alnoor says, grid loading, and any kind of access where batches are enabled (also a grid) is quite slow on Advanced in V2019 - 2021.  (We didn't have this issue in 2018 – it only started with v2019).  It does take between 6 and 10 seconds to load batches, when you're in a Data Entry screen where batches have been enabled. When you're trying to print anything where a batch has been enabled, folks end up clicking on a menu item multiple times, thinking their first "click" didn't register.  Eventually, the batch screen comes up, but then so do 3 or 4 others where the client clicked the menu item again.  Double clicking on an Invoice in AR used to take no time at all to load, and now you can count to at least 6 before that invoice comes to the screen.

Sage thought they had narrowed the problem down to the client's Remote RDP access, but turns out they didn't clear their redirected printers when they tested.  (And re-directed printers is also an issue on Advanced – we've solved that by using TS Print however, and that works well.)  So – it wasn't the remote app after all.  And – sadly - we did just receive a note from Nathan Shaw, after he had tested the client data for a little over a week.  And the note said: "We can duplicate the problem, but we've discussed the issue with Engineering and there is nothing that can be done.  So, there is nothing we can do to speed up the system." 

That's it.  That's all we have – as I mentioned, our IT Team is still attempting to see if the problem is with the Terminal Server or not – but something did indeed change with V2019.

Sue Bennett | President

Bennett/Porter & Associates, Inc.

P. 503 620 3484 | F. 503 620 2765

12559 SW 69th Ave | Portland, OR  97223

Email address | www.benpor.com

Bennett/Porter Blog | facebook | twitter

The information in this email and any attachments is considered confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

As Alnoor says, grid loading, and any kind of access where batches are enabled (also a grid) is quite slow on Advanced in V2019 - 2021.  (We didn't have this issue in 2018 – it only started with v2019).  It does take between 6 and 10 seconds to load batches, when you're in a Data Entry screen where batches have been enabled. When you're trying to print anything where a batch has been enabled, folks end up clicking on a menu item multiple times, thinking their first "click" didn't register.  Eventually, the batch screen comes up, but then so do 3 or 4 others where the client clicked the menu item again.  Double clicking on an Invoice in AR used to take no time at all to load, and now you can count to at least 6 before that invoice comes to the screen.

Sage thought they had narrowed the problem down to the client's Remote RDP access, but turns out they didn't clear their redirected printers when they tested.  (And re-directed printers is also an issue on Advanced – we've solved that by using TS Print however, and that works well.)  So – it wasn't the remote app after all.  And – sadly - we did just receive a note from Nathan Shaw, after he had tested the client data for a little over a week.  And the note said: "We can duplicate the problem, but we've discussed the issue with Engineering and there is nothing that can be done.  So, there is nothing we can do to speed up the system." 

That's it.  That's all we have – as I mentioned, our IT Team is still attempting to see if the problem is with the Terminal Server or not – but something did indeed change with V2019.

Sue Bennett | President

Bennett/Porter & Associates, Inc.

P. 503 620 3484 | F. 503 620 2765

12559 SW 69th Ave | Portland, OR  97223

Email address | www.benpor.com

Bennett/Porter Blog | facebook | twitter

The information in this email and any attachments is considered confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

As Alnoor says, grid loading, and any kind of access where batches are enabled (also a grid) is quite slow on Advanced in V2019 - 2021.  (We didn't have this issue in 2018 – it only started with v2019).  It does take between 6 and 10 seconds to load batches, when you're in a Data Entry screen where batches have been enabled. When you're trying to print anything where a batch has been enabled, folks end up clicking on a menu item multiple times, thinking their first "click" didn't register.  Eventually, the batch screen comes up, but then so do 3 or 4 others where the client clicked the menu item again.  Double clicking on an Invoice in AR used to take no time at all to load, and now you can count to at least 6 before that invoice comes to the screen.

Sage thought they had narrowed the problem down to the client's Remote RDP access, but turns out they didn't clear their redirected printers when they tested.  (And re-directed printers is also an issue on Advanced – we've solved that by using TS Print however, and that works well.)  So – it wasn't the remote app after all.  And – sadly - we did just receive a note from Nathan Shaw, after he had tested the client data for a little over a week.  And the note said: "We can duplicate the problem, but we've discussed the issue with Engineering and there is nothing that can be done.  So, there is nothing we can do to speed up the system." 

That's it.  That's all we have – as I mentioned, our IT Team is still attempting to see if the problem is with the Terminal Server or not – but something did indeed change with V2019.

Sue Bennett | President

Bennett/Porter & Associates, Inc.

P. 503 620 3484 | F. 503 620 2765

12559 SW 69th Ave | Portland, OR  97223

Email address | www.benpor.com

Bennett/Porter Blog | facebook | twitter

The information in this email and any attachments is considered confidential. This information may be subject to legal, professional, or other privilege. It must not be disclosed to any person without our authority. If you are not the intended recipient you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. Please return this message to the sender immediately and delete any and all copies from your system.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.

Two things I can think of

1.       Make sure that they have been moved to the subscription based pricing.  I made the mistake of telling a client that they could move to the Advanced Platform without any Sage fees, only to discover that this was one of our clients that chose not to move to subscription pricing. They were still on maintenance, but not on subscription and Sage wanted over 10k to switch to the Advanced Platform. I had to go back to the client and break the news to them. Of course it goes back onto them for not switching, but I still wish I would have checked before telling them.

2.       Scripting – we moved a client to Advanced and they had written their own scripts with pop-ups and message boxes (some asking for user-input). Message boxes work differently in advanced so the message box scripts had to be modified to work on Advanced. The "user-input" pop-ups had to be changed significantly to work on advanced; those we changed to use UDF on the screen where the user entered the input prior to running the script.