Sage 100

For general automated reporting: Visual Cut.

https://milletsoftware.com/Visual_CUT.htm 

If you need new / changed record functionality, that is part of the ActionQ software (which can trigger parameterized reports based on the new / changed data).

https://milletsoftware.com/ActionQ.htm

We have VC installed at dozens of clients, and it is reliable / easy to use / cost effective. There is a webinar recording in the Google drive somewhere I believe.

ActionQ is newer and with a less-than-pretty interface, but it works well for the handful of clients we use it for.

@Kevin Moyes do either of these provide alerts to employees when the next step is ready for a workflow process?

For general automated reporting: Visual Cut.

https://milletsoftware.com/Visual_CUT.htm 

If you need new / changed record functionality, that is part of the ActionQ software (which can trigger parameterized reports based on the new / changed data).

https://milletsoftware.com/ActionQ.htm

We have VC installed at dozens of clients, and it is reliable / easy to use / cost effective. There is a webinar recording in the Google drive somewhere I believe.

ActionQ is newer and with a less-than-pretty interface, but it works well for the handful of clients we use it for.

Would you have a source for this: 

"They are not going to make it compatible with 64 bit ODBC. "

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
------------------------------

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

@Beth Bowers, just realized you said it is your client that David Speck made it work on.

1) Was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

2) Has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

Sage hasn't experienced any issues, but I wouldn't expect it to, since Alerts doesn't write back, as far as I know.

@Beth Bowers, just realized you said it is your client that David Speck made it work on.

1) Was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

2) Has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

The workflow portion of Sage Alerts (& Workflow) does write back to Sage.  We have quite a few clients that have work flow processes (like PO Approvals) that when the user receives an SAW Email they respond and it updates fields in Sage Purchase Order (as an example).  In that case, we have SAW on a different server than the APP Server (in our case they are also SQL so it is installed on the SQL Server). 

Sage hasn't experienced any issues, but I wouldn't expect it to, since Alerts doesn't write back, as far as I know.

@Beth Bowers, just realized you said it is your client that David Speck made it work on.

1) Was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

2) Has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

The workflow portion of Sage Alerts (& Workflow) does write back to Sage.  We have quite a few clients that have work flow processes (like PO Approvals) that when the user receives an SAW Email they respond and it updates fields in Sage Purchase Order (as an example).  In that case, we have SAW on a different server than the APP Server (in our case they are also SQL so it is installed on the SQL Server). 

Sage hasn't experienced any issues, but I wouldn't expect it to, since Alerts doesn't write back, as far as I know.

@Beth Bowers, just realized you said it is your client that David Speck made it work on.

1) Was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

2) Has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

@Madeline StefanouIt sounds like since the 32 bit ODBC driver will still be installed, then SAW will continue to work.  I am definitely hearing for the Advanced version of Sage to put it on a different server.  Can you tell me what kind of issues you have seen so I can tell my client?

The workflow portion of Sage Alerts (& Workflow) does write back to Sage.  We have quite a few clients that have work flow processes (like PO Approvals) that when the user receives an SAW Email they respond and it updates fields in Sage Purchase Order (as an example).  In that case, we have SAW on a different server than the APP Server (in our case they are also SQL so it is installed on the SQL Server). 

Sage hasn't experienced any issues, but I wouldn't expect it to, since Alerts doesn't write back, as far as I know.

@Beth Bowers, just realized you said it is your client that David Speck made it work on.

1) Was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

2) Has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

The ODBC drivers provided by Sage are read-only.  If anyone is writing to a Providex based system through ODBC, they must be providing a read/write driver.

@Madeline StefanouIt sounds like since the 32 bit ODBC driver will still be installed, then SAW will continue to work.  I am definitely hearing for the Advanced version of Sage to put it on a different server.  Can you tell me what kind of issues you have seen so I can tell my client?

The workflow portion of Sage Alerts (& Workflow) does write back to Sage.  We have quite a few clients that have work flow processes (like PO Approvals) that when the user receives an SAW Email they respond and it updates fields in Sage Purchase Order (as an example).  In that case, we have SAW on a different server than the APP Server (in our case they are also SQL so it is installed on the SQL Server). 

Sage hasn't experienced any issues, but I wouldn't expect it to, since Alerts doesn't write back, as far as I know.

@Beth Bowers, just realized you said it is your client that David Speck made it work on.

1) Was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

2) Has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

Michele,

I only realized at a later point the Sage version they came from (I don't know what that actually was sorry) was also 64-bit and they already had a 32-bit ODBC System DSN for K-Sync setup and working on that Sage server.

No K-Sync/Sage Alerts has not created any issues with Sage 64-bit before or after the upgrade. Now I did not know K-Sync writes back to Sage, and for this client they wouldn't need that. But if you're telling me K-Sync can be set up to write back and does so using a Read-Write version of the ODBC driver (instead of BOI), that is news to me.

Thank you so much @Kevin Moyes, @Alnoor Cassim, @Beth Bowers and @Wayne Schulz.

1) @David Speck II, did you do the same process as Alnoor?

     I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I then went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage was still successfully running 64-bit ODBC.

2)  @David Speck II and @Alnoor Cassim, was your client already using Sage Alerts and Work Flow on a 32 bit version of Sage 100 when you converted them to the 64 bit version of Sage 100?  If yes, did you experience any issues with Sage by having it connected to Sage Alerts and Work Flow?

3) @David Speck II and @Alnoor Cassim has having Sage Alerts and Workflow connected to Sage created any issues with Sage?  Like writing back to Sage?

I posted a question for Sage to confirm the plan... *fingers crossed*

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/265332/v2026-and-32-bit-odbc

I haven't spent a lot of time researching this however one item I came across had the same suggestion as @Alnoor Cassim that the 64-bit might have to be searched for rather than presented as the default.

Michele - On a recent upgrade to v2024 Advanced I was helping somebody with, Sage 64-bit was installed; ergo, the 64-bit ODBC driver was being used by Sage and by the Crystal Reports designer. However, 64-bit created the problem with KnowledgeSync / Sage Alerts issue you mentioned. However, I noticed when I went to the 32-bit ODBC administrator (c:\windows\sysWOW64\odbcad32.exe) that the Drivers tab showed "MAS 90 4.0 ODBC Driver" was available. I went to the System DSN tab and was able to successfully create the 32-bit silent connect DSN that KnowledgeSync wanted and we were good to go, all while Sage and Crystal designer were still successfully running 64-bit ODBC.

So I'm saying you may also see the 32-bit ODBC driver installed on your 64-bit Sage. Hopefully.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

If our client is SQL (Sage 100 Premium); then we put Knowledge Sync on the SQL Server since we don't have to instlall a Sage 100 Wkstn Client there, and it usually works just fine. 

If our client is Advanced, if we have a different server to put it on we do.  If not, we use the App Server and it does sometimes cause issues.  v2026 will install both 32-Bit ODBC and 64-Bit ODBC, so it should not be an issue; right? 

Our Developer spoke with Greg Swallow and the technical resource Alex from KnowledgeSync. Here is a recap of the call.  They will be putting something in the documentation as well but wanted to get this to you before.   

• KnowledgeSync/Sage Alert does not support 64 bit ODBC drivers for Sage 100 and they do not have any plans on supporting it because of the work around available.  64 Bit linked SQL server is supported and can run on SQL Express.
• While Sage 100 does provide a 32/64 bit ODBC driver the issue has more to do with the 64 bit Crystal Designer not seeing the 32 bit DSN so unless the Crystal report was designed in a 32 bit designer this will cause an issue.
• The work around is to create a Linked Server (64 bit) so both the Crystal report data source can be changed to OLEDB and the Ksync can also use the same SQL connection.
• The only caveat here is that the Syntax in queries will change so DateDiff for example works differently with the ACCESS and PVX driver than the SQL driver.
• We have seen some Crystal Runtime errors as well so I think the recommendation would still be to try and put Sage Alerts on a server separate from Sage 100 but this may depend on the version of Sage 100.
• I have been able to get around these errors by uninstalling the 64 bit runtime and re-installing the 32 bit runtime. 

If our client is SQL (Sage 100 Premium); then we put Knowledge Sync on the SQL Server since we don't have to instlall a Sage 100 Wkstn Client there, and it usually works just fine. 

If our client is Advanced, if we have a different server to put it on we do.  If not, we use the App Server and it does sometimes cause issues.  v2026 will install both 32-Bit ODBC and 64-Bit ODBC, so it should not be an issue; right? 

It has been a while, but we used to use BPA Platform (fka Task Centre).  Paul Cannon and Nicolle Laurier used to come to MOTM.  

As another alternative (especially if you have access to an IT / Techie types), I would create PowerShell scripts that ran SQL queries (looking for some condition) using Windows Task Scheduler to schedule them. Both of those tools are free outside the labor.

It has been a while, but we used to use BPA Platform (fka Task Centre).  Paul Cannon and Nicolle Laurier used to come to MOTM.  

FYI - For clients using providex, Knowledgesync now has a SQL based version that is best for providex clients that are new to Knowledgesync.  Since this will version can use either the full version of SQL or SQL Express, I'm thinking it would be ok on the same server as the Sage 100 Advanced install.  Access will not be involved.  Any thoughts on this?

As another alternative (especially if you have access to an IT / Techie types), I would create PowerShell scripts that ran SQL queries (looking for some condition) using Windows Task Scheduler to schedule them. Both of those tools are free outside the labor.

It has been a while, but we used to use BPA Platform (fka Task Centre).  Paul Cannon and Nicolle Laurier used to come to MOTM.  

Sage announced earlier this week during that partner call that the 64-bit issue had been resolved.  Is this what they meant?

FYI - For clients using providex, Knowledgesync now has a SQL based version that is best for providex clients that are new to Knowledgesync.  Since this will version can use either the full version of SQL or SQL Express, I'm thinking it would be ok on the same server as the Sage 100 Advanced install.  Access will not be involved.  Any thoughts on this?

As another alternative (especially if you have access to an IT / Techie types), I would create PowerShell scripts that ran SQL queries (looking for some condition) using Windows Task Scheduler to schedule them. Both of those tools are free outside the labor.

It has been a while, but we used to use BPA Platform (fka Task Centre).  Paul Cannon and Nicolle Laurier used to come to MOTM.  

That was a separate issue.  For the providex platforms of Sage, an Access database had to be used vs. a SQL database.  There is now a newer version of Knowledgesync that uses a SQL database with the Sage providex platform.  So, I'm thinking it should be fine being on the same server as Sage 100.

Sage announced earlier this week during that partner call that the 64-bit issue had been resolved.  Is this what they meant?

FYI - For clients using providex, Knowledgesync now has a SQL based version that is best for providex clients that are new to Knowledgesync.  Since this will version can use either the full version of SQL or SQL Express, I'm thinking it would be ok on the same server as the Sage 100 Advanced install.  Access will not be involved.  Any thoughts on this?

As another alternative (especially if you have access to an IT / Techie types), I would create PowerShell scripts that ran SQL queries (looking for some condition) using Windows Task Scheduler to schedule them. Both of those tools are free outside the labor.

It has been a while, but we used to use BPA Platform (fka Task Centre).  Paul Cannon and Nicolle Laurier used to come to MOTM.