Kbase 15342: VBX Support Policy
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
Explanation of Progress support policies for Visual Basic custom control (VBX).
FACT(s) (Environment):
Progress 8.x
FIX:
Progress support for VBXs in Version 8.x is as follows:
VBXs were initially created for developing Windows applications
with Visual Basic. Many different companies offer specialized
VBXs for tasks such as controlling instruments or image handling.
VBXs are superseded by the more flexible ActiveX controls.
VBX and OLE are standards, and as such, different vendors
interpret them or support them in differing ways. For this
reason, you might find that VBXs and OLE objects from one vendor
can work better than those from another.
Progress cannot guarantee that Version 8.x works with every VBX
or OLE object because there is no guarantee of how other vendors
comply with the standards.
Supporting for VBXs included with Version 8.x:
Enhanced combo, spin control, and timer control are fully
supported. The OLE control is supported but it might not
work with applications that are not implemented to the
correct OLE standards.
Support for Crescent VBXs:
All Crescent controls are no longer supported by Progress
Technical Support. Refer to the Sax Software Web site that
can be reached at http://www.saxsoft.com.
Support for third party VBXs:
Without a standard specification for Visual Basic Control
containers, Progress cannot guarantee that all VBX controls
are fully supported.
If a feature of a Visual Basic control is not working,
technical support establishes if the feature of the VBX
control functions correctly under Visual Basic. If the
control works correctly under Visual Basic, Progress
requires the name of the vendor of the control, the
vendor's phone number and a description of the problem.
You cannot be guaranteed the issue can be resolved because of the lack of specifications for VBX control containers,
and the differences between the Visual Basic and Progress
architecture.
Technical support always investigates as far as possible
without leaving you in-between two vendors that might argue
with each other.
Progress Version 8.x includes VBX support at the following level:
- The use of Visual Basic Controls up to VBX Level 2, and
some support for VBX Level 3.
- Nested VBXs (VBXs contained within other VBXs), Data Bound
Controls and Graphical Controls (lines and circles for
example) are not supported, but you might be able to use
some of the features.
For example, you can place a VBX that supports data
binding in a Progress application, but the data binding
features of that control do not function. Everything
else functions, however. (You must use 4GL code to
integrate the VBX with a data source).
One nested VBX that is not guaranteed to work is the
TabPro VBX.
Progress ProVision Version 8.x bundles the following
VBXs:
- Enhanced combo (from Crescent QuickPak Pro, originally).
- Spin control (from Crescent QuickPak Pro, originally).
- Timer control.
- OLE container control.
(Might not work with applications that are not
implemented to the correct OLE standards.)
Progress tested Version 8.x with all but a few of the VBXs
included in Crescent's QuickPak Pro and PowerPak Pro products. If
you want to add VBXs to your Progress applications, contact Sax Software at:
http://www.saxsoft.com
Some VBXs in the Crescent products were never tested because they
are heavily oriented towards Visual Basic and are not used by
most, .if any, Progress developers (VBXs that are designed to
customize the Visual Basic development environment, for example).
Progress tested several 3rd party VBXs from companies like
Sheridan, Spyworks, Videosoft, and Microsoft..