Sage 100

John, I think you are saying these are two separate issues - the Fixed Assets v2023 install seems to conflict with Sage 100 2022 or earlier due to the FA use of Crystal 2020.

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

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


Original Message:
Sent: 05-04-2023 08:47
From: Wayne Schulz
Subject: v2023 Upgrade Issues

John, I think you are saying these are two separate issues - the Fixed Assets v2023 install seems to conflict with Sage 100 2022 or earlier due to the FA use of Crystal 2020.

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

Please post any 2023 issues on this thread so we can monitor problems/observations easily

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


Original Message:
Sent: 05-04-2023 08:47
From: Wayne Schulz
Subject: v2023 Upgrade Issues

John, I think you are saying these are two separate issues - the Fixed Assets v2023 install seems to conflict with Sage 100 2022 or earlier due to the FA use of Crystal 2020.

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

Please post any 2023 issues on this thread so we can monitor problems/observations easily

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


Original Message:
Sent: 05-04-2023 08:47
From: Wayne Schulz
Subject: v2023 Upgrade Issues

John, I think you are saying these are two separate issues - the Fixed Assets v2023 install seems to conflict with Sage 100 2022 or earlier due to the FA use of Crystal 2020.

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

great idea @Jeff Schwenk  Most of my clients have third party add on products, so I'm holding off until June/July I guess.

Please post any 2023 issues on this thread so we can monitor problems/observations easily

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


Original Message:
Sent: 05-04-2023 08:47
From: Wayne Schulz
Subject: v2023 Upgrade Issues

John, I think you are saying these are two separate issues - the Fixed Assets v2023 install seems to conflict with Sage 100 2022 or earlier due to the FA use of Crystal 2020.

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

Guess I am going slowly this time around.  With new version of Crystal that may not play well with others, a new Amyuni driver and the temptation to jump into the 64 bit water, I am starting with the BLS system first.

BTW, with the new Amyuni driver (AND differnt device printer name), can you delete the previous one (will the new driver work in pre 2023 versions)?

great idea @Jeff Schwenk  Most of my clients have third party add on products, so I'm holding off until June/July I guess.

Please post any 2023 issues on this thread so we can monitor problems/observations easily

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


Original Message:
Sent: 05-04-2023 08:47
From: Wayne Schulz
Subject: v2023 Upgrade Issues

John, I think you are saying these are two separate issues - the Fixed Assets v2023 install seems to conflict with Sage 100 2022 or earlier due to the FA use of Crystal 2020.

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

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Having a consolidated list would be useful... but is there a way to set up email notifications for changes to a Google Doc?  How will people find it?

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Hi Kevin - I am going to do both a Google Doc (with actual posts copied for cross-reference) and a Spreadsheet.  Both can have notifications of any updates as well as posted comments.   With the spreadsheet - you can even request a daily digest.  

If someone has a better suggestion - I am always open.  We do have a team beginning to work in the background on content retention so I am hoping to get some assistance. Thanks! 

Having a consolidated list would be useful... but is there a way to set up email notifications for changes to a Google Doc?  How will people find it?

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Suggestion ( Small / Medium / Large options )

Small: 

• Create a shareable master document where everyone who has the link can see the document
• Create links off this screen to additional documents ( so there's only one spot to check )

Medium:

• Post the above document to an email alert

Large

• Have users obtain paid Google Workspace account ( $144/yr) to actively participate in edits/maintenance
• This could always been reimbursed if the user is active for a period of time

I am not successful enough searching Higher Logic to think that HL or a mass email chain will be enough 

Hi Kevin - I am going to do both a Google Doc (with actual posts copied for cross-reference) and a Spreadsheet.  Both can have notifications of any updates as well as posted comments.   With the spreadsheet - you can even request a daily digest.  

If someone has a better suggestion - I am always open.  We do have a team beginning to work in the background on content retention so I am hoping to get some assistance. Thanks! 

Having a consolidated list would be useful... but is there a way to set up email notifications for changes to a Google Doc?  How will people find it?

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

So the big question (based on the round table discussion today) is SHOULD we be installing 64 bit Sage as a default?  What are the downsides?  It didn't sound like @Beth Bowers & @Jeff Fiddelman are experiencing any.  Sage Intelligence issues?  What about Starship and the myriad of other enhancements?  I recall Beth having issues with the Avalara 64 DLLs(?) last year.  Resolved?  Any push back about not being able to use the old 32 bit versions of Sage? 

TIA

Suggestion ( Small / Medium / Large options )

Small: 

• Create a shareable master document where everyone who has the link can see the document
• Create links off this screen to additional documents ( so there's only one spot to check )

Medium:

• Post the above document to an email alert

Large

• Have users obtain paid Google Workspace account ( $144/yr) to actively participate in edits/maintenance
• This could always been reimbursed if the user is active for a period of time

I am not successful enough searching Higher Logic to think that HL or a mass email chain will be enough 

Hi Kevin - I am going to do both a Google Doc (with actual posts copied for cross-reference) and a Spreadsheet.  Both can have notifications of any updates as well as posted comments.   With the spreadsheet - you can even request a daily digest.  

If someone has a better suggestion - I am always open.  We do have a team beginning to work in the background on content retention so I am hoping to get some assistance. Thanks! 

Having a consolidated list would be useful... but is there a way to set up email notifications for changes to a Google Doc?  How will people find it?

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

So the big question (based on the round table discussion today) is SHOULD we be installing 64 bit Sage as a default?  What are the downsides?  It didn't sound like @Beth Bowers & @Jeff Fiddelman are experiencing any.  Sage Intelligence issues?  What about Starship and the myriad of other enhancements?  I recall Beth having issues with the Avalara 64 DLLs(?) last year.  Resolved?  Any push back about not being able to use the old 32 bit versions of Sage? 

TIA

Suggestion ( Small / Medium / Large options )

Small: 

• Create a shareable master document where everyone who has the link can see the document
• Create links off this screen to additional documents ( so there's only one spot to check )

Medium:

• Post the above document to an email alert

Large

• Have users obtain paid Google Workspace account ( $144/yr) to actively participate in edits/maintenance
• This could always been reimbursed if the user is active for a period of time

I am not successful enough searching Higher Logic to think that HL or a mass email chain will be enough 

Hi Kevin - I am going to do both a Google Doc (with actual posts copied for cross-reference) and a Spreadsheet.  Both can have notifications of any updates as well as posted comments.   With the spreadsheet - you can even request a daily digest.  

If someone has a better suggestion - I am always open.  We do have a team beginning to work in the background on content retention so I am hoping to get some assistance. Thanks! 

Having a consolidated list would be useful... but is there a way to set up email notifications for changes to a Google Doc?  How will people find it?

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

I asked during the call about 32-bit and 64-bit being able to co-exist on the same server.  Elliott said he'd look into it.

For a lot of our upgrades we do a test migration, meaning we are basically forced to 32-bit (so the old version is not broken by the new version install).

Sage wants to push 64-bit, and while the list of issues is shrinking, the technical hurdles are not all gone yet.

So the big question (based on the round table discussion today) is SHOULD we be installing 64 bit Sage as a default?  What are the downsides?  It didn't sound like @Beth Bowers & @Jeff Fiddelman are experiencing any.  Sage Intelligence issues?  What about Starship and the myriad of other enhancements?  I recall Beth having issues with the Avalara 64 DLLs(?) last year.  Resolved?  Any push back about not being able to use the old 32 bit versions of Sage? 

TIA

Suggestion ( Small / Medium / Large options )

Small: 

• Create a shareable master document where everyone who has the link can see the document
• Create links off this screen to additional documents ( so there's only one spot to check )

Medium:

• Post the above document to an email alert

Large

• Have users obtain paid Google Workspace account ( $144/yr) to actively participate in edits/maintenance
• This could always been reimbursed if the user is active for a period of time

I am not successful enough searching Higher Logic to think that HL or a mass email chain will be enough 

Hi Kevin - I am going to do both a Google Doc (with actual posts copied for cross-reference) and a Spreadsheet.  Both can have notifications of any updates as well as posted comments.   With the spreadsheet - you can even request a daily digest.  

If someone has a better suggestion - I am always open.  We do have a team beginning to work in the background on content retention so I am hoping to get some assistance. Thanks! 

Having a consolidated list would be useful... but is there a way to set up email notifications for changes to a Google Doc?  How will people find it?

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

Once you're live, you can run the conversion between 32 and 64.

I asked during the call about 32-bit and 64-bit being able to co-exist on the same server.  Elliott said he'd look into it.

For a lot of our upgrades we do a test migration, meaning we are basically forced to 32-bit (so the old version is not broken by the new version install).

Sage wants to push 64-bit, and while the list of issues is shrinking, the technical hurdles are not all gone yet.

So the big question (based on the round table discussion today) is SHOULD we be installing 64 bit Sage as a default?  What are the downsides?  It didn't sound like @Beth Bowers & @Jeff Fiddelman are experiencing any.  Sage Intelligence issues?  What about Starship and the myriad of other enhancements?  I recall Beth having issues with the Avalara 64 DLLs(?) last year.  Resolved?  Any push back about not being able to use the old 32 bit versions of Sage? 

TIA

Suggestion ( Small / Medium / Large options )

Small: 

• Create a shareable master document where everyone who has the link can see the document
• Create links off this screen to additional documents ( so there's only one spot to check )

Medium:

• Post the above document to an email alert

Large

• Have users obtain paid Google Workspace account ( $144/yr) to actively participate in edits/maintenance
• This could always been reimbursed if the user is active for a period of time

I am not successful enough searching Higher Logic to think that HL or a mass email chain will be enough 

Hi Kevin - I am going to do both a Google Doc (with actual posts copied for cross-reference) and a Spreadsheet.  Both can have notifications of any updates as well as posted comments.   With the spreadsheet - you can even request a daily digest.  

If someone has a better suggestion - I am always open.  We do have a team beginning to work in the background on content retention so I am hoping to get some assistance. Thanks! 

Having a consolidated list would be useful... but is there a way to set up email notifications for changes to a Google Doc?  How will people find it?

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)

I don't believe we can but I will look into it tomorrow. 

Hey @Robert Wood - Looks like there are two threads for v2023 issues.  Can you combine them?

Another twist on an outdated Crystal Runtime Engine 32 bit.  Trying to install Sage v2023 on the server.  Not sure why the program can't detect the existing older version and install it......

In case you encounter this issue while printing a report, save yourself some time.  Uninstall the workstation client AND the two Crystal runtime engines.  Reinstall the WS client.  The issue also impacted v2022 printing.

Sage patched something related to Standard Prereq's.
Link.

Not sure if it is me or my clients or Sage.  The 2023 client installs are taking a long time installing the prerequisites!!

I've noticed Sage referring to the 2023 versions with different names. I suspect this mirrors those names.

Argh, apparently the Sage 100 v2023 Service names have changed for some reason! 🙄  Why does Sage do things like this?!  I heard about this from another Consultant; haven't yet seen it first-hand.

- Advanced says "Standard"
- Premium says "Advanced"
- And I guess Standard is now "StandAlone/LAN"

Ther school of hard knocks.  Home of the best teachers!

Reminds me of learning the hard way that the Reversal button is only available in Account MAINTENANCE, not INQUIRY...

NEVER MIND!!!!!  After migrating, be sure to check role maintenance for new security permissions!!!!!!!!!!  Another 45 minutes of non productive time.....

Trying to access 1099 fields in AP Vendor maintenance.  Fields are "locked" and I am unable to access.  Since I had screen modifications, I disabled those and tried again.  Crickets.  I verified 1099 was on in Option set up.  Turned it off.  Saved.  Re-enabled.  Crickets.  Changed 1099 year to current.  Nothing.  Works fine in v2022.  I rebuilt the custom panels in CO.

Can someone test and let me know if it works or is this a bug?

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


Original Message:
Sent: 05-05-2023 08:54
From: Jeff Schwenk
Subject: v2023 Upgrade Issues

Any ramifications in using Crystal 2020 to create/modify reports for pre 2023 Sage?

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


Original Message:
Sent: 05-04-2023 12:19
From: Kevin Moyes
Subject: v2023 Upgrade Issues

Interesting.  On day 1 I installed v2023 on a test machine (having multiple older versions already installed) and had no issues with printing at all.  (After the Sage 100 v2023 install I can print from v2021, 2019, 2017, 2015... all Standard, all 32-bit).
I saw the prompt that the new CR engine was being installed, but I don't know if it was successful.  (This machine doesn't have SFA).
I believe there are issues with Crystal Reports engine 32-bit vs 64-bit not being cross compatible, so maybe that's what you ran into?
Are those 3 independent sources all trying out 64-bit at the same time?

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

I know, but I'd also have to change the service... and if the old version is still online (for reference), that could break it. 

Scheduled VI jobs in batch files: update from pvxwin32.exe to pvxwin64.exe... 

Lots of little extra little re-work details, for questionable gains.

Changing later (if encountering the Win11 issue) is just as easy then.

Once you're live, you can run the conversion between 32 and 64.

I asked during the call about 32-bit and 64-bit being able to co-exist on the same server.  Elliott said he'd look into it.

For a lot of our upgrades we do a test migration, meaning we are basically forced to 32-bit (so the old version is not broken by the new version install).

Sage wants to push 64-bit, and while the list of issues is shrinking, the technical hurdles are not all gone yet.

So the big question (based on the round table discussion today) is SHOULD we be installing 64 bit Sage as a default?  What are the downsides?  It didn't sound like @Beth Bowers & @Jeff Fiddelman are experiencing any.  Sage Intelligence issues?  What about Starship and the myriad of other enhancements?  I recall Beth having issues with the Avalara 64 DLLs(?) last year.  Resolved?  Any push back about not being able to use the old 32 bit versions of Sage? 

TIA

Suggestion ( Small / Medium / Large options )

Small: 

• Create a shareable master document where everyone who has the link can see the document
• Create links off this screen to additional documents ( so there's only one spot to check )

Medium:

• Post the above document to an email alert

Large

• Have users obtain paid Google Workspace account ( $144/yr) to actively participate in edits/maintenance
• This could always been reimbursed if the user is active for a period of time

I am not successful enough searching Higher Logic to think that HL or a mass email chain will be enough 

Hi Kevin - I am going to do both a Google Doc (with actual posts copied for cross-reference) and a Spreadsheet.  Both can have notifications of any updates as well as posted comments.   With the spreadsheet - you can even request a daily digest.  

If someone has a better suggestion - I am always open.  We do have a team beginning to work in the background on content retention so I am hoping to get some assistance. Thanks! 

Having a consolidated list would be useful... but is there a way to set up email notifications for changes to a Google Doc?  How will people find it?

Why not just throw the details on a shareable Google Doc that can be maintained. Then it won't matter how many threads are started or if comments about v2023 are left in an unrelated thread as you can just share that master document.

@Jeff Schwenk and @Robert Wood

Unfortunately, you can only move a thread and not move any individual posts or merge threads.  

However, here is the link to the prior discussion for reference in this thread: 

V2023 Issues | Sage 100 (90minds.com)