| Title: | ACMS comments and questions |
| Notice: | This is not an official software support channel. Kits 5.* |
| Moderator: | CLUSTA::HALL AN |
| Created: | Mon Feb 17 1986 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4179 |
| Total number of notes: | 15091 |
Hi all, We are creating a new interface for an existing DEC-forms / ACMS program. It will run in Visual Basic 4.0. We want to use the ACMS-tasks from the "old" system, but we don't use DEC-forms anymore. Instead we are creating a web-based interface with ASP (Active Server Pages). Currently the main ACMS-task is started. It will end when the program is finished. But during this task there is a lot of communication between ACMS and DEC-forms performed by this main ACMS-task. We want to start the main ACMS-task (with Visual Basic) and then "trap" the communication meant for DEC-forms because we don't use DEC-forms, but we use Visual Basic. So we want all things happening on the screen to go to Visual Basic in stead of DEC-forms. So, all current screen-things: EXCHANGE WORK IS TRANSCEIVE FROM RECORD SENDING ... RECEIVING ... will currently go to DEC-forms. Is there a way to "trap" this from within Visual Basic? Your help will be appreciated... Greetings, Mike Wiering & Arjan Sikkema [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4129.1 | ACMS::HALL | Bill Hall - ACMS Engineering - ZKO2-2 | Wed Mar 19 1997 05:45 | 9 | |
You should take a look at the Desktop ACMS product. It provides
a way of interfacing non-character cell based terminals (PC's, MAC's,
etc) to an existing ACMS system with little or no modifications to
existing tasks. The product descriptions can be found off of
Digitals external web page (www.digital.com).
Bill
| |||||