Input Pro 3.0 Fixed Problems - Technical Support

Input Pro 3.0 Fixed Problems

The problem tracking number appears after the description in parentheses. Where two numbers are given, the new number appears first followed by the original number from the older tracking system.

Select Edit->Find in the browser menu to search for a particular keyword or tracking number.

| Version 3.0.39 | Version 3.0.38 | Version 3.0.37 | Version 3.0.36 |
| Version 3.0.35 | Version 3.0.30 | Version 3.0.25 | Version 3.0.21 |
| Version 3.0.20 | Version 3.0.11 | Version 3.0.10 | Version 3.0.07 |

Technical Issues Addressed—Release Date 6/9/2009—Version 3.0.39
All controls

The controls now work correctly with Microsoft Vista and Visual Studio 2008. (25446)

Technical Issues Addressed—Release Date 9/4/2007—Version 3.0.38
fpMask control

The mask control now works correctly on an mdi form. (11808)

The focus now works correctly with the control and menus. (19337)

The AllowOverFlow property now works correctly when binding the control. (20821)

fpText control

The right alt-z and right alt-n keys now work correctly with Polish keyboard settings. (9518)

Technical Issues Addressed—Release Date 11/1/2006—Version 3.0.37
fpCurrency control

The currency control now uses the decimal symbol from the currency tab. (18539)

The edit cursor now works properly with decimal values when the UseSeparator property is true. (19307)

Technical Issues Addressed—Release Date 3/15/2006—Version 3.0.36
fpBoolean control

The control no longer causes a memory leak when closing the form. (9079)

fpDateTime control

The IsValid property now returns the correct value from the Validate event. (9585)

The control now works correctly with dual monitors. (12366)

If the control resolves the date to a valid date then it no longer shows the IsValid property as False. (17535)

fpLongInteger control

The RawValue property now returns the correct value. (13954)

fpMemo control

Adding blank lines with code now works correctly if the WordWrap property is True. (11249)

The user can no longer paste into the control if the ControlType property is set to ReadOnly. (15950)

Technical Issues Addressed—Release Date 11/5/2003—Version 3.0.35
fpDateTime control

The taskbar no longer displays a blank button for the drop-down calendar displayed from the fpDateTime control. (10638)

The control now correctly displays the AM/PM string when the international or regional settings include the string in the time format. (12461)

fpDoubleSingle control

Typing a decimal value when the number in the control is selected now correctly replaces the selected value. (11853)

Pressing Backspace to move over existing values, and then typing new values, no longer incorrectly moves the cursor to after the decimal point. (11900)

With the DecimalPlaces property set to 2, typing a single digit in the control now displays a single digit instead of a digit and decimal (for example, "3" instead of "3.0"). (12113)

fpMemo control

When WordWrap is set to True, highlighting text and then using the shortcut keys "Ctrl+X," "Ctrl+V," and "Ctrl+Z" no longer causes the control to freeze. (11940)

Double-clicking on the control when the ControlType property is set to 2 (Static) no longer freezes the application. (12232)

fpText control

The Advance event is no longer firing both when it leaves an fpText control and when it enters another. (11965)

The down arrow now works correctly and moves the focus to the next control from an fpText control that has the following settings set at design time: the AllowNull property set to True, Text set to "", the MultiLine property set to True, and the AutoAdvance property set to True. (11970)

Technical Issues Addressed—Release Date 2/13/2001—Version 3.0.30
All controls except fpBoolean control

The pointer is now correctly changing when the control's ControlType property is set to 3 (Button Edit). (11008)

fpCurrency control

The cursor position is now updated correctly when the LeadZero property is set to 1 (No Leading Zero) or the regional settings are set to not display a leading zero. (9410, 10558)

The control now accepts decimal values correctly when its AllowNull property is set to True and the value in the control is Null. (9796)

fpDateTime control

When the UserEntry property is set to 1 (Free Format), the control now correctly allows free format user entry after the user presses F2 to clear the data. (8605)

Pressing the Backspace key no longer deletes characters in a formatted DateTime control. (9931)

fpDoubleSingle control

The cursor position is now updated correctly when the LeadZero property is set to 1 (No Leading Zero) or the regional settings are set to not display a leading zero. (9410, 10558)

The Change event now occurs correctly when the value in the control is zero, the cursor is between the zero and the decimal point, and the user changes the value. (9700)

The control now correctly accepts decimal values when the regional settings for decimal values are set to not display a leading zero. (10558)

fpMemo control

Multiple line feeds now work correctly in the control. (9392)

Clicking on the scroll bar when the control does not have the focus now correctly updates line positions. (9430)

The Text property now returns the correct text from controls that contain a blank line when the TextMode property is set to 3 (Line). (9848)

Pasting text in the control that would cause the text to exceed the LineLimit property setting now works correctly. (9853)

Technical Issues Addressed—Release Date 9/20/2001—Version 3.0.25
All controls

Using an Input Pro control in Excel or a VBA environment no longer causes an undefined error message. (8471/SCS9400)

Several focus issues with the OLE drag and drop feature were fixed. (8542/SCS9618)

The control's Validate event now occurs correctly when moving focus between the Input Pro control and a control on a different form. (8446/CHB6467)

All controls except fpBoolean control

Pressing the Delete key on the number pad when the control's ControlType property is set to 1 (Read-Only) and the AllowNull property is True no longer deletes data in the control. (9290)

The control no longer affects the Windows default ButtonFace color when it is not intended. (8681/GIC12577)

fpCurrency control

The control now correctly lets users enter null values. (8618/GIC12276)

You can now set the minimum value to an exponential value, as in previous versions of Input Pro. (8695/SCS10159)

Unloading a control in its Change event no longer causes problems in Visual Basic. (9311)

The control is now properly accepting typed data when it displays a separator character and is in Overwrite mode. (9323)

fpDateTime control

The Change event now occurs correctly when the control inserts the current date in place of an invalid value. (8711/GIC12698)

The control no longer causes problems in Visual Basic when the DateMax and DateMin properties are set to the default (00000000) and the control's date is set to 12/31/9999. (8723/TIB7760)

The control now correctly lets users type leap year dates into the control. (9097)

fpDoubleSingle control

You can now set the minimum value to an exponential value, as in previous versions of Input Pro. (8695/SCS10159)

Typing a negative sign before typing a number no longer changes the number entered by the user. (8680/SCS10128)

The control now correctly lets users enter null values. (8618/GIC12276)

Unloading a control in its Change event no longer causes problems in Visual Basic. (9311)

The control is now properly accepting typed data when it displays a separator character and is in Overwrite mode. (9323)

fpLongInteger control

The control now correctly lets users enter null values. (8555/GIC12009)

Unloading a control in its Change event no longer causes problems in Visual Basic. (9311)

fpMask control

The control now correctly accepts input after data is cut from the control. (8666/SCS10081)

fpMemo control

The control is no longer inserting an extra blank line in text when the control moves the cursor to a specified line using the CurrentLine property. (9195)

Scrolling is now working properly when characters are covered by the vertical scroll bar. (5183/SCS8428)

fpText control

The control no longer lets users insert a linefeed by pressing the Enter key when the ControlType property is set to 1 (Read Only) or 3 (Button Edit) and the MultiLine property is set to True. (8539/SCS9606)

The AutoCase property is now working correctly when set to 4 (Proper with Upper). (8537/GIC11936)

The KeyDown event is now occuring correctly. (9212)

The AutoBeep capability is now working correctly when users try to type more characters than are allowed by the setting of the MaxLength property. (6113)

Technical Issues Addressed—Release Date 5/25/2000—Version 3.0.21
All controls

Printing a form in Microsoft® Visual Basic® when the form contains Input Pro controls no longer causes Visual Basic to stop responding. (GIC12058)

fpBoolean control

The DblClick event now occurs correctly for the fpBoolean control. (TIB6831)

fpCurrency control

The UnFmtText property now correctly returns the value in a control in response to the Change event. Previously, when the control's UserEntry property was set to 1 (Free Format) and the user returned the value in response to the Change event, an incorrect value was returned. (SCS9501)

Technical Issues Addressed—Release Date 3/14/2000—Version 3.0.20
All controls

Previous to this release, printing an HTML page that contained Input Pro controls from Internet Explorer resulted in some of the controls printing very small. This release fixes that problem, and the controls now print correctly. (SCS9362)

Loading during the Form_Initialize phase of project loading has been optimized. (CHB6418)

The BackColor property now returns a long variant type in Visual Basic 6, similar to Input Pro releases before Input Pro 3.0. (SCS9467)

Access no longer displays a license error when an Input Pro control is on an Access 2000 form. (SCS9479)

fpBoolean control

Problems that arose when binding an fpBoolean control to a byte field in a database have been resolved. In addition, the BooleanDataType property now provides a setting to use when binding to byte and numeric fields: setting 3 (Number). (TIB5824)

The fpBoolean control is now writing the correct value to a SQL Server database bound using the RDO data control. (GRB7474)

Users can now move the focus to the control using an access key when the control is checked or grayed. (SCS9364)

fpCurrency control

Controls with that are set to be static (ControlType property is set to 2, Static), now correctly prevent users from pressing the Tab key to send focus to the control. (SCS8931)

The control now lets the user input the decimal character in the intended position, regardless of the setting of the UserEntry property. (SCS9195)

The user can now type values less than 1 when the MinValue property is set to 0.0001 and the AllowNull property is set to True. (CHB6298)

Pressing the decimal symbol key when a decimal value (between 0 and 1) is in the control now correctly replaces the value in the control. (TIB6406)

You can now use the SelStart and the SelLength properties in the DblClick event to highlight text in the control. To do so, set the Button parameter to 0. (CHB6658)

fpDateTime control

Controls with that are set to be static (ControlType property is set to 2, Static), now correctly prevent users from pressing the Tab key to send focus to the control. (SCS8931)

Pressing Ctrl+Z to undo a key sequence no longer causes a general protection fault. (GRB9094)

The control is now letting users input dates correctly when the regional settings are set to dd.MM.yyyy. (CHB6475)

The control is no longer letting users change the date by pressing the up or down arrow keys when the ControlType property is set to 1 (Read Only). (TIB6463)

The control now correctly sets the time value from a pop-up clock when the AllowNull property is set to True, the DateTimeFormat property is set to 4 (Time Only), the text is set to "", and the UserEntry property is set to 0 (Formatted). (GIC11738)

You can now use the SelStart and the SelLength properties in the DblClick event to highlight text in the control. To do so, set the Button parameter to 0. (CHB6658)

fpDoubleSingle control

Controls with that are set to be static (ControlType property is set to 2, Static), now correctly prevent users from pressing the Tab key to send focus to the control. (SCS8931)

The control now lets the user input the decimal character in the intended position, regardless of the setting of the UserEntry property. (SCS9195)

The user can now type values less than 1 when the MinValue property is set to 0.0001 and the AllowNull property is set to True. (CHB6298)

Pressing the decimal symbol key when a decimal value (between 0 and 1) is in the control now correctly replaces the value in the control. (TIB6406)

You can now use the SelStart and the SelLength properties in the DblClick event to highlight text in the control. To do so, set the Button parameter to 0. (CHB6658)

fpLongInteger control

Controls with that are set to be static (ControlType property is set to 2, Static), now correctly prevent users from pressing the Tab key to send focus to the control. (SCS8931)

You can now use the SelStart and the SelLength properties in the DblClick event to highlight text in the control. To do so, set the Button parameter to 0. (CHB6658)

fpMask control

Controls with that are set to be static (ControlType property is set to 2, Static), now correctly prevent users from pressing the Tab key to send focus to the control. (SCS8931)

In certain situations, closing a form that contains an fpMask control caused Visual Basic 6.0 to hang. That problem no longer occurs. (SCS8891)

You can now use the SelStart and the SelLength properties in the DblClick event to highlight text in the control. To do so, set the Button parameter to 0. (CHB6658)

fpMemo control

The PageWidth property now correctly uses the measurement unit indicated by the Form's ScaleMode property. (CHB5530)

Accessing the property pages for the control in Visual C++ 6.0 no longer causes VC++ to stop responding. (SCS9001)

Deleting text in a bound fpMemo control now correctly deletes the text in the corresponding record in the database. (JUW624)

The control now correctly allows users to insert or replace text in the control without causing an error where the control mistakenly thinks the LineCount will exceed the LineLimit setting. (CHB6465)

fpText control

Controls with that are set to be static (ControlType property is set to 2, Static), now correctly prevent users from pressing the Tab key to send focus to the control. (SCS8931)

The user can now select text in the control correctly using either the keyboard or the mouse. (CHB6272)

You can now use the SelStart and the SelLength properties in the DblClick event to highlight text in the control. To do so, set the Button parameter to 0. (CHB6658)

Technical Issues Addressed—Release Date 8/19/99—Version 3.0.11
fpCurrency control

The MaxValue and MinValue properties no longer add "00" to the end of the setting when the properties are set programmatically, in the Visual Basic property window, or in the property designer. (JUW471)

The control now replaces text correctly when the integer portion is 0 and the user selects text in the decimal portion and then types data to replace the selected text. (GRB7465)

fpDoubleSingle control

The MaxValue and MinValue properties no longer add "00" to the end of the setting when the properties are set programmatically, in the Visual Basic property window, or in the property designer. (JUW471)

The control now replaces text correctly when the integer portion is 0 and the user selects text in the decimal portion and then types data to replace the selected text. (GRB7465)

fpLongInteger control

The MaxValue and MinValue properties no longer add "00" to the end of the setting when the properties are set programmatically, in the Visual Basic property window, or in the property designer. (JUW471)

Technical Issues Addressed—Release Date 8/2/99—Version 3.0.10
fpCurrency control

Previous to release 3.0.10, the MaxValue and MinValue properties for the fpCurrency and fpDoubleSingle controls required you to type in decimal values using a period (".") as the decimal symbol, no matter the setting of the DecimalPoint property.

Starting with release 3.0.10, the MaxValue and MinValue properties require you to type in the decimal values using the decimal symbol specified by the DecimalPoint property. Therefore, if your project has settings for the MaxValue and MinValue properties and your project uses a value other than the period (".") for the DecimalPoint property, you must update the settings of the MaxValue and MinValue properties to use the decimal symbol specified by the DecimalPoint property. (GRB7443)

Typing the decimal symbol now correctly enters the decimal symbol in the fpCurrency and fpDoubleSingle controls, and the control correctly handles values entered in a control displaying a decimal symbol. (JUW115, GRB7442)

The control is now properly handling text selection when the OnFocusSelect property is set to True and the user moves the focus to the control by using the mouse. (CHB5682)

fpDateTime control

The control now properly removes the pop-up or drop-down calendar when the user tabs to another control. (GIC9580)

fpDateTime controls bound to Access databases now correctly save data to the database table when it is entered in a previously Null field. (TIB5455)

The Value property is now correctly setting the value for fpDateTime controls. (SCS8755)

The control is now properly handling text selection when the OnFocusSelect property is set to True and the user moves the focus to the control by using the mouse. (CHB5682)

fpDoubleSingle control

Previous to release 3.0.10, the MaxValue and MinValue properties for the fpCurrency and fpDoubleSingle controls required you to type in decimal values using a period (".") as the decimal symbol, no matter the setting of the DecimalPoint property.

Starting with release 3.0.10, the MaxValue and MinValue properties require you to type in the decimal values using the decimal symbol specified by the DecimalPoint property. Therefore, if your project has settings for the MaxValue and MinValue properties and your project uses a value other than the period (".") for the DecimalPoint property, you must update the settings of the MaxValue and MinValue properties to use the decimal symbol specified by the DecimalPoint property. (GRB7443)

Typing the decimal symbol now correctly enters the decimal symbol in the fpCurrency and fpDoubleSingle controls, and the control correctly handles values entered in a control displaying a decimal symbol. (JUW115, GRB7442)

The control is now properly handling text selection when the OnFocusSelect property is set to True and the user moves the focus to the control by using the mouse. (CHB5682)

fpLongInteger control

The control is now properly handling text selection when the OnFocusSelect property is set to True and the user moves the focus to the control by using the mouse. (CHB5682)

fpMask control

The control is now properly handling text selection when the OnFocusSelect property is set to True and the user moves the focus to the control by using the mouse. (CHB5682)

fpText control

The control is now properly handling text selection when the OnFocusSelect property is set to True and the user moves the focus to the control by using the mouse. (CHB5682)

Technical Issues Addressed—Release Date 6/22/99—Version 3.0.07
fpBoolean control

The fpBoolean control now has the Value property as the default property in Visual Basic, as it did in releases of Input Pro prior to Input Pro 3.0.

fpMask control

The fpMask control now has the Text property as the default property in Visual Basic, as it did in releases of Input Pro prior to Input Pro 3.0.