| Title: | DECtp Desktop for ACMS |
| Moderator: | UCROW::GIBSON |
| Created: | Mon Sep 24 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 859 |
| Total number of notes: | 3034 |
My customer is experiencing problems using 32 bit Visual Basic.
They get an error - Run time error 453:Specified DLL function not found.
They claim that they are OK using 16 bit Visual Basic.
Their software line-up is as follows:
VB4 32 bit development
ACMSDI V2.0
NT 3.51
TCP/IP
ACMS V4.0-0
I notice that their ACMSDI DLL files are all dated late 1985.
Is it time to upgrade to version 2.2 of ACMS DESKTOP.
I also see that the SPD 38.81.11 does not make a claim to support
Visual Basic under NT for ACMS and OPENVMS, or am I reading it wrong.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 840.1 | it does work | SIOG::KEYES | Digital Appliation Gen. DTN 827-2705 | Wed Apr 09 1997 08:09 | 13 |
Check out note 723 for more details.
Certainly NT 3.51 based clients can work with ACMS and OpenVMS. 16 bit
is of course fine..Though 32 bit is slightly more complicated (723
has many details).
Dates on yoyur DLL's would suggest you are using incorrect ones
rgs
mick
| |||||
| 840.2 | Need to upgrade for VB4 32 bit. | UCROW::GIBSON | Wed Apr 09 1997 08:27 | 26 | |
VB4 32 bit support is provided in the form of a workaround using a
helper DLL until such time as we can more fully address its
requirements. The helper DLL was not done until after V2.2 shipped.
The communication protocol between the clients and server was revised
in V2.1 (unix server code base). That means in order to use the V2.2
clients your customer will also need to upgrade the server from V2.0 to
V2.2 and then install the ECO. This is because older servers can not
talk to newer clients across a mismatched communciation protocol
revision level.
The first thing is to read and make available to the customer as you
see fit information about the helper DLL. See
ucrow::acms_desktop$pubdir:[v22.vb4].
Then the alternatives are:
1) Wait until V2.3 is available out of the SSB sometime in May.
It will have the clients, VB4 helper write up and matching server
all together on the one kit along with the V2.3 enhancements.
2) Install V2.2 on the server and the clients.
Install V2.2 ECO1 on both the server and the clients. See on ucrow
acms_desktop$pubdir:[v22.eco1].
/Tom
| |||||