Sage 100

Does anyone regularly use the "Automatic Logoff" feature in Sage 100? I don't believe that I have ever turned it on for any customer.

The reason I ask is because ee have a long-standing customer that uses Sage 100 in an EazyApp environment and recently they have hired new people (including new managers).  Some of these people can't be bothered with properly logging out of Sage 100 nor properly disconnecting from the EazyApp server.  I now have EazyApp configured to automatically disconnect them after two idle hours.  I was thinking about having Sage log them out at 110 minutes.

After some testing, I have determined that when the session times out Sage will check for unsaved open entries.  If there are open entries, then the system will give a selection box with the following options:

• Click Yes to save changes and close the window
• Click No to close the window without saving changes
• Click Cancel to close the message and leave the window open

My testing has shown that Batches and Entry Headers will be saved but if no one is present to select "Yes" to save the changes then the system defaults to "No" and the lines of the entry aren't saved.  That's fine with me.

My big question is if anyone has seen any data corruption by using this feature over a long period of time.

Thank you for your input. 

------------------------------
Chuck Peddy
Smartbridge Partners
------------------------------

I'd like to learn the logic of retaining headers only.

Are the headers complete, i.e. include customer number and other required header information?  I find many clients with incomplete Sales Orders missing customer numbers that hang out there until I come along and delete them.  I attribute this to dropped sessions. Could they be caused by auto logoff?

------------------------------
Bob Pfahnl
Manager - Silicon Valley
DSD Business Systems
------------------------------

I have a few customers using it. I am not a big fan of it as I keep getting my session closed because I am doing more than one thing and by the time I cycle back to them my session is closed and everything is closed. I do not think I have seen data corruption from it. Most of these customers have been using it for 5 years or more this way.

I do think the current versions of Sage handle the closing better than they did in the past. I can't recall for sure, but I think when it first was introduced, we had issues with it, and I tried to keep most of the customers from using it. But in the past 5 years or so it hasn't been an issue. Header records I believe are created as soon as you get the next order number. it populates the header with the required fields populated. This header isn't removed unless you cancel or delete (answer the prompt when it goes to close). When the system drops due to inactivity, it doesn't delete what was created. It just drops the session and everything that was in memory is gone. I am guessing the logic is to do least destructive which would be to not delete what was started but to just loose what was in memory. This way nothing is changed or removed that already existed. I would think that the system would keep those until you use the order number again. You would have to key that number in as the next order number will skip it since it was already incremented. I could see this being an issue over time having a lot of Sales Orders without customer number or any real info.

------------------------------
Todd Martin
MBA Business Software
https://www.mbabsi.com
------------------------------

Hi All, this caught my attention today.   I am doing an upgrade to 2024 Advanced.   The client is going from Work Order to PM.  They have been using Sage (MAS90) since 1996 so tons of history.   I left the conversion running. When I checked back it was no longer running. Found that the conversion did not complete (modules showing 4.50 as the data level).  Then I remembered that they use Autologoff & that my account was set to close after 2 hours.  In the past I have been able to restart conversions and have them complete successfully but not in this case. It completes but when I go into the system I says it needs to be converted.  I noticed that Work Order was still listed as a module for the company (at version 7.0). I wound up trying another company (after turning off the autologoff) and it converted ok. 

  So two things - Auto logoff doesn't care what you are doing apparently  and if a WO to PM conversion fails, you will need to start over.  

------------------------------
Bob Osborn
Senior Consultant
DSD
7142645278
------------------------------

My SOP for doing conversions is running in MAS 90 mode from the server.  Keeps things simple.  Yes, it doesn't work from Premium but very few clients of mine run premium.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!
------------------------------

Original Message:
Sent: 06-28-2025 11:57
From: Robert Osborn
Subject: Automatic Logoff

Hi All, this caught my attention today.   I am doing an upgrade to 2024 Advanced.   The client is going from Work Order to PM.  They have been using Sage (MAS90) since 1996 so tons of history.   I left the conversion running. When I checked back it was no longer running. Found that the conversion did not complete (modules showing 4.50 as the data level).  Then I remembered that they use Autologoff & that my account was set to close after 2 hours.  In the past I have been able to restart conversions and have them complete successfully but not in this case. It completes but when I go into the system I says it needs to be converted.  I noticed that Work Order was still listed as a module for the company (at version 7.0). I wound up trying another company (after turning off the autologoff) and it converted ok. 

  So two things - Auto logoff doesn't care what you are doing apparently  and if a WO to PM conversion fails, you will need to start over.  

------------------------------
Bob Osborn
Senior Consultant
DSD
7142645278
------------------------------

Jeff, MAS90 mode does indeed work for Premium, the same way as Advanced.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 06-28-2025 18:03
From: Jeff Schwenk
Subject: Automatic Logoff

My SOP for doing conversions is running in MAS 90 mode from the server.  Keeps things simple.  Yes, it doesn't work from Premium but very few clients of mine run premium.

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!
------------------------------


Original Message:
Sent: 06-28-2025 11:57
From: Robert Osborn
Subject: Automatic Logoff

Hi All, this caught my attention today.   I am doing an upgrade to 2024 Advanced.   The client is going from Work Order to PM.  They have been using Sage (MAS90) since 1996 so tons of history.   I left the conversion running. When I checked back it was no longer running. Found that the conversion did not complete (modules showing 4.50 as the data level).  Then I remembered that they use Autologoff & that my account was set to close after 2 hours.  In the past I have been able to restart conversions and have them complete successfully but not in this case. It completes but when I go into the system I says it needs to be converted.  I noticed that Work Order was still listed as a module for the company (at version 7.0). I wound up trying another company (after turning off the autologoff) and it converted ok. 

  So two things - Auto logoff doesn't care what you are doing apparently  and if a WO to PM conversion fails, you will need to start over.  

------------------------------
Bob Osborn
Senior Consultant
DSD
7142645278

Interesting information @Robert Osborn.  Good think to double check before starting data conversions. Thank you. 

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 06-28-2025 11:57
From: Robert Osborn
Subject: Automatic Logoff

Hi All, this caught my attention today.   I am doing an upgrade to 2024 Advanced.   The client is going from Work Order to PM.  They have been using Sage (MAS90) since 1996 so tons of history.   I left the conversion running. When I checked back it was no longer running. Found that the conversion did not complete (modules showing 4.50 as the data level).  Then I remembered that they use Autologoff & that my account was set to close after 2 hours.  In the past I have been able to restart conversions and have them complete successfully but not in this case. It completes but when I go into the system I says it needs to be converted.  I noticed that Work Order was still listed as a module for the company (at version 7.0). I wound up trying another company (after turning off the autologoff) and it converted ok. 

  So two things - Auto logoff doesn't care what you are doing apparently  and if a WO to PM conversion fails, you will need to start over.  

------------------------------
Bob Osborn
Senior Consultant
DSD
7142645278
------------------------------

If one of our clients enabled auto-logoff for the Sage login we use when performing system maintenance / admin activities, I would immediately disable it and tell them to leave our admin level Sage 100 login alone.  If we leave something running, it is for a good reason.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 06-28-2025 11:57
From: Robert Osborn
Subject: Automatic Logoff

Hi All, this caught my attention today.   I am doing an upgrade to 2024 Advanced.   The client is going from Work Order to PM.  They have been using Sage (MAS90) since 1996 so tons of history.   I left the conversion running. When I checked back it was no longer running. Found that the conversion did not complete (modules showing 4.50 as the data level).  Then I remembered that they use Autologoff & that my account was set to close after 2 hours.  In the past I have been able to restart conversions and have them complete successfully but not in this case. It completes but when I go into the system I says it needs to be converted.  I noticed that Work Order was still listed as a module for the company (at version 7.0). I wound up trying another company (after turning off the autologoff) and it converted ok. 

  So two things - Auto logoff doesn't care what you are doing apparently  and if a WO to PM conversion fails, you will need to start over.  

------------------------------
Bob Osborn
Senior Consultant
DSD
7142645278
------------------------------