Sage 100

The "HERE" for questions isn't working for me, nor is the ability to answer the question about a new report.

The "HERE" for questions isn't working for me, nor is the ability to answer the question about a new report.

One comment about the new L/S stuff, which I hadn't noticed already existed in the current Sage - Product Line Maintenance.  I think the Accounts tab should be third - I know they hate changing anything, but if they can finally move the Delete tab to be #2 in Delete and Change, they can put the Accounts tab last in Product Line Maintenance.  Just makes more sense not to breakup the other options.

The "HERE" for questions isn't working for me, nor is the ability to answer the question about a new report.

@Beth Bowers agree. It is logical for items that are default for new items, but actually assigned at the item level to be the 1st 2 tabs, leaving accounts last (that are not item level assignments)

One comment about the new L/S stuff, which I hadn't noticed already existed in the current Sage - Product Line Maintenance.  I think the Accounts tab should be third - I know they hate changing anything, but if they can finally move the Delete tab to be #2 in Delete and Change, they can put the Accounts tab last in Product Line Maintenance.  Just makes more sense not to breakup the other options.

The "HERE" for questions isn't working for me, nor is the ability to answer the question about a new report.

I'm not sure if this is an appropriate place to post "quick wins" but Sage should update the following message that pops up after form printing. It is confusing for new users that have never seen or heard of "module options" in Role Maintenance. 

@Beth Bowers agree. It is logical for items that are default for new items, but actually assigned at the item level to be the 1st 2 tabs, leaving accounts last (that are not item level assignments)

One comment about the new L/S stuff, which I hadn't noticed already existed in the current Sage - Product Line Maintenance.  I think the Accounts tab should be third - I know they hate changing anything, but if they can finally move the Delete tab to be #2 in Delete and Change, they can put the Accounts tab last in Product Line Maintenance.  Just makes more sense not to breakup the other options.

The "HERE" for questions isn't working for me, nor is the ability to answer the question about a new report.

Dear Development,

We need to talk. This problem has been going on far too long and we are both pretending not to notice the obvious. 

Looking the other way and pretending it's not happening isn't good for us ( the consultants ), you ( the developers ) or them ( our mutual clients ). 

The elephant in the room? 

It's workstation setup. And more specifically paperless office and how difficult it is to ensure that once you've run workstation setup on a standalone desktop that paperless is going to work. 

Let me insert a pause here so my wiser colleagues can jump in and reassure me (and you) that this is not never a problem for them. 

It's not a problem because it's masked by brute force and quoting (or burying this overhead) 2 hours per workstation for install, manual testing and follow-up on workstation setup.  Let's take a typical sized Sage 100 customer --- 2 hours x 20 workstations x 200/hr = $8,000 implied cost just to babysit a workstation setup?

Sure, some of these paperless office setup issues are documented in the knowledgebase - scattered through about a dozen "try this, try that" type articles many of which are two or more years old. 

And you can create a "cheat sheet" for IT to walk workstation to workstation and follow your steps. This helps cut down costs. But it's embarrassing that after almost 40 years on the market that this type of "grind it out" installation of workstations is acceptable.

AI is going to rewrite kb articles into one master document. This will help except the client's IT department still goes workstation to workstation stomping out Error 30 or Error 41 or Printer Not Activated messages... but why should there have to be a lengthy checklist? We are installing basic workstation setups for an accounting system and not starting up the engines on a 767 to take 300 passengers on an overseas flight.

Please let's come up with a workable solution so that running workstation setup also reliably configures the paperless office for the current version of Sage 100.

Thank you for your attention to this matter.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------

@Wayne Schulz So, are you saying there could be room for improvement?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------


Original Message:
Sent: 07-25-2025 09:28
From: Wayne Schulz
Subject: Upcoming: Sage Development Roundtable - Thursday August 7, 2025

Dear Development,

We need to talk. This problem has been going on far too long and we are both pretending not to notice the obvious. 

Looking the other way and pretending it's not happening isn't good for us ( the consultants ), you ( the developers ) or them ( our mutual clients ). 

The elephant in the room? 

It's workstation setup. And more specifically paperless office and how difficult it is to ensure that once you've run workstation setup on a standalone desktop that paperless is going to work. 

Let me insert a pause here so my wiser colleagues can jump in and reassure me (and you) that this is not never a problem for them. 

It's not a problem because it's masked by brute force and quoting (or burying this overhead) 2 hours per workstation for install, manual testing and follow-up on workstation setup.  Let's take a typical sized Sage 100 customer --- 2 hours x 20 workstations x 200/hr = $8,000 implied cost just to babysit a workstation setup?

Sure, some of these paperless office setup issues are documented in the knowledgebase - scattered through about a dozen "try this, try that" type articles many of which are two or more years old. 

And you can create a "cheat sheet" for IT to walk workstation to workstation and follow your steps. This helps cut down costs. But it's embarrassing that after almost 40 years on the market that this type of "grind it out" installation of workstations is acceptable.

AI is going to rewrite kb articles into one master document. This will help except the client's IT department still goes workstation to workstation stomping out Error 30 or Error 41 or Printer Not Activated messages... but why should there have to be a lengthy checklist? We are installing basic workstation setups for an accounting system and not starting up the engines on a 767 to take 300 passengers on an overseas flight.

Please let's come up with a workable solution so that running workstation setup also reliably configures the paperless office for the current version of Sage 100.

Thank you for your attention to this matter.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

When i say that Paperless Office debugging is a lot of "try this, try that" and refers to old (confusing) and sometimes outdated KB entries - here's my inspiration. 

@Wayne Schulz So, are you saying there could be room for improvement?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 07-25-2025 09:28
From: Wayne Schulz
Subject: Upcoming: Sage Development Roundtable - Thursday August 7, 2025

Dear Development,

We need to talk. This problem has been going on far too long and we are both pretending not to notice the obvious. 

Looking the other way and pretending it's not happening isn't good for us ( the consultants ), you ( the developers ) or them ( our mutual clients ). 

The elephant in the room? 

It's workstation setup. And more specifically paperless office and how difficult it is to ensure that once you've run workstation setup on a standalone desktop that paperless is going to work. 

Let me insert a pause here so my wiser colleagues can jump in and reassure me (and you) that this is not never a problem for them. 

It's not a problem because it's masked by brute force and quoting (or burying this overhead) 2 hours per workstation for install, manual testing and follow-up on workstation setup.  Let's take a typical sized Sage 100 customer --- 2 hours x 20 workstations x 200/hr = $8,000 implied cost just to babysit a workstation setup?

Sure, some of these paperless office setup issues are documented in the knowledgebase - scattered through about a dozen "try this, try that" type articles many of which are two or more years old. 

And you can create a "cheat sheet" for IT to walk workstation to workstation and follow your steps. This helps cut down costs. But it's embarrassing that after almost 40 years on the market that this type of "grind it out" installation of workstations is acceptable.

AI is going to rewrite kb articles into one master document. This will help except the client's IT department still goes workstation to workstation stomping out Error 30 or Error 41 or Printer Not Activated messages... but why should there have to be a lengthy checklist? We are installing basic workstation setups for an accounting system and not starting up the engines on a 767 to take 300 passengers on an overseas flight.

Please let's come up with a workable solution so that running workstation setup also reliably configures the paperless office for the current version of Sage 100.

Thank you for your attention to this matter.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

Dear Development,

We need to talk. This problem has been going on far too long and we are both pretending not to notice the obvious. 

Looking the other way and pretending it's not happening isn't good for us ( the consultants ), you ( the developers ) or them ( our mutual clients ). 

The elephant in the room? 

It's workstation setup. And more specifically paperless office and how difficult it is to ensure that once you've run workstation setup on a standalone desktop that paperless is going to work. 

Let me insert a pause here so my wiser colleagues can jump in and reassure me (and you) that this is not never a problem for them. 

It's not a problem because it's masked by brute force and quoting (or burying this overhead) 2 hours per workstation for install, manual testing and follow-up on workstation setup.  Let's take a typical sized Sage 100 customer --- 2 hours x 20 workstations x 200/hr = $8,000 implied cost just to babysit a workstation setup?

Sure, some of these paperless office setup issues are documented in the knowledgebase - scattered through about a dozen "try this, try that" type articles many of which are two or more years old. 

And you can create a "cheat sheet" for IT to walk workstation to workstation and follow your steps. This helps cut down costs. But it's embarrassing that after almost 40 years on the market that this type of "grind it out" installation of workstations is acceptable.

AI is going to rewrite kb articles into one master document. This will help except the client's IT department still goes workstation to workstation stomping out Error 30 or Error 41 or Printer Not Activated messages... but why should there have to be a lengthy checklist? We are installing basic workstation setups for an accounting system and not starting up the engines on a 767 to take 300 passengers on an overseas flight.

Please let's come up with a workable solution so that running workstation setup also reliably configures the paperless office for the current version of Sage 100.

Thank you for your attention to this matter.

We haven't yet hit the 32/64-bit deadline (yet). Shouldn't the install routine for 2025 warn the user if - during the start of an upgrade - a 64-bit version of Sage 100 is already installed to the server? As it stands now - at least for Sage 100 2025 - there is no warning. I didn't get far enough to know what, if any, issues would occur if the customer was running Sage 100 64-bit already and I guessed wrong and installed Sage 100 32-bit as part of my upgrade. I know the 32-to-64 bit utility exists and is easy to run however it seems like there should be some type of system check during the upgrade.

Hi everyone - here is a link to the one question asked by the Sage Team.  Can you respond before Monday? Thanks! 

SD Survey

We haven't yet hit the 32/64-bit deadline (yet). Shouldn't the install routine for 2025 warn the user if - during the start of an upgrade - a 64-bit version of Sage 100 is already installed to the server? As it stands now - at least for Sage 100 2025 - there is no warning. I didn't get far enough to know what, if any, issues would occur if the customer was running Sage 100 64-bit already and I guessed wrong and installed Sage 100 32-bit as part of my upgrade. I know the 32-to-64 bit utility exists and is easy to run however it seems like there should be some type of system check during the upgrade.

(Broken link... Do you require a new report for Lot Code Source tracking? If so, what information should be included?).

Hi everyone - here is a link to the one question asked by the Sage Team.  Can you respond before Monday? Thanks! 

SD Survey

We haven't yet hit the 32/64-bit deadline (yet). Shouldn't the install routine for 2025 warn the user if - during the start of an upgrade - a 64-bit version of Sage 100 is already installed to the server? As it stands now - at least for Sage 100 2025 - there is no warning. I didn't get far enough to know what, if any, issues would occur if the customer was running Sage 100 64-bit already and I guessed wrong and installed Sage 100 32-bit as part of my upgrade. I know the 32-to-64 bit utility exists and is easy to run however it seems like there should be some type of system check during the upgrade.

Thanks Kevin - 

Here is the fixed link:  https://forms.gle/BihLf77FtiUT3QHw5

(Broken link... Do you require a new report for Lot Code Source tracking? If so, what information should be included?).

Hi everyone - here is a link to the one question asked by the Sage Team.  Can you respond before Monday? Thanks! 

SD Survey

We haven't yet hit the 32/64-bit deadline (yet). Shouldn't the install routine for 2025 warn the user if - during the start of an upgrade - a 64-bit version of Sage 100 is already installed to the server? As it stands now - at least for Sage 100 2025 - there is no warning. I didn't get far enough to know what, if any, issues would occur if the customer was running Sage 100 64-bit already and I guessed wrong and installed Sage 100 32-bit as part of my upgrade. I know the 32-to-64 bit utility exists and is easy to run however it seems like there should be some type of system check during the upgrade.

August 6th is on a WEDNESDAY.

Is meeting Wednesday August 5th OR

Thursday August 7th?

Thanks

Thanks Kevin - 

Here is the fixed link:  https://forms.gle/BihLf77FtiUT3QHw5

(Broken link... Do you require a new report for Lot Code Source tracking? If so, what information should be included?).

Hi everyone - here is a link to the one question asked by the Sage Team.  Can you respond before Monday? Thanks! 

SD Survey

My observation is that 90% of these meetings ends with a heavy Sage sigh.

Yeah. We. Have. To. Do. Better.

( Observation: It's always someone ELSE who has to do better ).

I signed up but something came up and I missed it. Is there a recording somewhere?