Major VB 6 Software Change in Sage 500 2024

While we were setting up development environments for Sage 500 2024, we ran into an issue with the Sheridan 3D controls for the VB6 source code.  Discussing with Sage, it seems Windows 11's 22H2 Smart App Control blocks the installation of the old Threed32.ocx.  Sage therefore swapped out this control library with the ActiveThreed Plus control library.  This library requires the purchase of a license to use for development.  Sage has the link to use if you wish to purchase this.

It would've been nice if Sage informed the 3rd party development community of this change as it is a pretty major change. It is possible to modify the source code to use the original Threed32.ocx, but you will be responsible for deploying and registering it on any target system where you install your modified VB 6 Sage source code.

Parents
  • 0

    That is my fault, after I made the changes at the beginning of version 2024 development completely forgot about the Release notes change related to this that I needed to make for the SDK.  We are in the process of making those changes now however the basics are below.

    With the possibility of Windows 11 operating systems having Smart App Control turned on the Threed32.ocx control is being blocked however the newer version of the control was able to be installed. We did have to move to a slightly newer control in version 2024.

    If you are modifying an application with the SDK that uses one of the affected controls, you will get a message Mentioning that the ActiveThreed control is in Demo Mode.

    With this change there are a couple of options.

    1. You could purchase a license of the “newer” version of the control. This control is unsupported, but you can still purchase a license at this link:

    ActiveThreed Plus (componentsource.com)

    2. If you don’t want to purchase a license and your clients are not running with Smart App Control turned on (this is not real common yet):

    You can modify your application to use the older version by the following steps.

    Not all projects use this control so this may not impact the applications you are working on.

    In the VBP file you are customizing you would want to change:

    Open the VBP in a text editor and find the following line.

    Object={065E6FD1-1BF9-11D2-BAE8-00104B9E0792}#3.0#0; ssa3d30.ocx

    Change it to the following line

    Object={0BA686C6-F7D3-101A-993E-0000C0EF6F5E}#1.0#0; THREED32.OCX

    Open the form files for the above project in a text editor and if the line below exists:

    Object = "{065E6FD1-1BF9-11D2-BAE8-00104B9E0792}#3.0#0"; "ssa3d30.ocx"

    Change it To the following line.

    Object = "{0BA686C6-F7D3-101A-993E-0000C0EF6F5E}#1.0#0"; "Threed32.ocx"

    And for the client machine(s) to be able to use that older version you would need to:

    Copy the Threed32.ocx from a machine with an old installation.

    C:\windows\syswow64\Threed32.ocx (typical location)

    And place on a 2024 installation machine in the same location and register it.

    If you don’t have a copy of that control (installed with versions prior to 2024) contact support and we can get you a copy.

    Again, I am sorry about this oversight,

    Kevin

Reply
  • 0

    That is my fault, after I made the changes at the beginning of version 2024 development completely forgot about the Release notes change related to this that I needed to make for the SDK.  We are in the process of making those changes now however the basics are below.

    With the possibility of Windows 11 operating systems having Smart App Control turned on the Threed32.ocx control is being blocked however the newer version of the control was able to be installed. We did have to move to a slightly newer control in version 2024.

    If you are modifying an application with the SDK that uses one of the affected controls, you will get a message Mentioning that the ActiveThreed control is in Demo Mode.

    With this change there are a couple of options.

    1. You could purchase a license of the “newer” version of the control. This control is unsupported, but you can still purchase a license at this link:

    ActiveThreed Plus (componentsource.com)

    2. If you don’t want to purchase a license and your clients are not running with Smart App Control turned on (this is not real common yet):

    You can modify your application to use the older version by the following steps.

    Not all projects use this control so this may not impact the applications you are working on.

    In the VBP file you are customizing you would want to change:

    Open the VBP in a text editor and find the following line.

    Object={065E6FD1-1BF9-11D2-BAE8-00104B9E0792}#3.0#0; ssa3d30.ocx

    Change it to the following line

    Object={0BA686C6-F7D3-101A-993E-0000C0EF6F5E}#1.0#0; THREED32.OCX

    Open the form files for the above project in a text editor and if the line below exists:

    Object = "{065E6FD1-1BF9-11D2-BAE8-00104B9E0792}#3.0#0"; "ssa3d30.ocx"

    Change it To the following line.

    Object = "{0BA686C6-F7D3-101A-993E-0000C0EF6F5E}#1.0#0"; "Threed32.ocx"

    And for the client machine(s) to be able to use that older version you would need to:

    Copy the Threed32.ocx from a machine with an old installation.

    C:\windows\syswow64\Threed32.ocx (typical location)

    And place on a 2024 installation machine in the same location and register it.

    If you don’t have a copy of that control (installed with versions prior to 2024) contact support and we can get you a copy.

    Again, I am sorry about this oversight,

    Kevin

Children
No Data