Skip to main content

[archive] Auto-complete ENTRY-FIELD

  • July 19, 2010
  • 2 replies
  • 0 views

[Migrated content. Thread originally posted on 15 July 2010]

Our users are becoming increasing vociferous about why we at UBCC are unable to offer auto-completion entry-fields as Intuit does in their Quicken & Quickbooks products.
If you aren't familiar with it, their auto-completion entry field looks like a combination entry-field/list box. As the operator types characters into the entry-field two things happen: The program suggests completion characters after the last character typed and a drop down list box appears with suggested values for the field. The operator can continue typing, press tab to take the automatic completion or click on any entry in the list box to fill the entry-field.
(The Google search entry provides a similar, simpler, version of the same type of control. It would be acceptable to us too.)
We are open to any suggestions including but not limited to ActiveX controls and other third party products or consulting services. We are looking to integrate this into our large inventory of AcuCobol GUI dependent programs, so for now .net and other replacements for the AcuCobol GUI are not our our first choices.
Regards,
Sal - UBCC Development

2 replies

[Migrated content. Thread originally posted on 15 July 2010]

Our users are becoming increasing vociferous about why we at UBCC are unable to offer auto-completion entry-fields as Intuit does in their Quicken & Quickbooks products.
If you aren't familiar with it, their auto-completion entry field looks like a combination entry-field/list box. As the operator types characters into the entry-field two things happen: The program suggests completion characters after the last character typed and a drop down list box appears with suggested values for the field. The operator can continue typing, press tab to take the automatic completion or click on any entry in the list box to fill the entry-field.
(The Google search entry provides a similar, simpler, version of the same type of control. It would be acceptable to us too.)
We are open to any suggestions including but not limited to ActiveX controls and other third party products or consulting services. We are looking to integrate this into our large inventory of AcuCobol GUI dependent programs, so for now .net and other replacements for the AcuCobol GUI are not our our first choices.
Regards,
Sal - UBCC Development
I suggest you consider being an extend 9.0 beta tester extend9.betacoordinator@microfocus.com
In 9.0 you can use or create .Net controls such as an listbox that has a checkboxes in it (that is the example that will be included in the beta), or any combination of .Net assemblies that you can find or create. extend 9.0 will go out to beta testers in mid August. The 9.0 release has a much better integration with .Net as compared to previous versions.

[Migrated content. Thread originally posted on 15 July 2010]

Our users are becoming increasing vociferous about why we at UBCC are unable to offer auto-completion entry-fields as Intuit does in their Quicken & Quickbooks products.
If you aren't familiar with it, their auto-completion entry field looks like a combination entry-field/list box. As the operator types characters into the entry-field two things happen: The program suggests completion characters after the last character typed and a drop down list box appears with suggested values for the field. The operator can continue typing, press tab to take the automatic completion or click on any entry in the list box to fill the entry-field.
(The Google search entry provides a similar, simpler, version of the same type of control. It would be acceptable to us too.)
We are open to any suggestions including but not limited to ActiveX controls and other third party products or consulting services. We are looking to integrate this into our large inventory of AcuCobol GUI dependent programs, so for now .net and other replacements for the AcuCobol GUI are not our our first choices.
Regards,
Sal - UBCC Development
Thanks. We will keep that in mind. We are not currently prepared to commit to a full replacement of our user interface so .Net would be an ideal or practical solution to our rather limited issue. I.e. In essence, we just need one more type of control. (We can probably code in COBOL what we need with a Entry-Field with Notify-Changed paired with a List-Box but would prefer to have the GUI machinery supplied in a bullet proof way way.)