Visual M is now a separate product. Visual M is also available with Open M for Windows 95 and NT. However, Visual M is no longer supplied with Open M [DTM]. You can still can use both Open M for Windows 95 and NT and Open M [DTM] as local Visual M Servers residing on the same computer as the Visual M Client.
You can use any of the following M implementations as Visual M Servers residing on a remote computer:
Version 7.0 of Visual M provides 32-bit Visual Basic 4.0 support for both the MVB and MDeskTop control. (The MDeskTop control is not supported under 16-bit Visual Basic 4.0.) You can use the MDeskTop control in almost the same way with 32-bit Visual Basic 4.0 as you did previously. However, there are a few differences brought about by the different architecture Visual Basic 4.0 provides.
A new ElapsedTime property has been added to the OCX MVB control for Visual Basic 4.0. ElapsedTime is a runtime, read-only property that gives a measurement of the elapsed time it takes to process a server request.
A new ErrorTrap property has been added to the OCX MVB control. ErrorTrap contains a truth value you can set to determine the scope of the errors you can trap
A new MsgText property has been added to the OCX MVB control. The MsgText property contains a four-piece string that specifies the displayed items in the cancel dialog box that appears if the amount of time specified in PromptInterval is reached.
A new PromptInterval property has been added to the OCX MVB control. The PromptInterval property works with the MsgText property to provide closer control over messages to the server that may take a long time. The PromptInterval property contains the number of milliseconds between the time a message is sent to the server and when a cancel dialog box is displayed. (You use MsgText to specify the contents of the dialog box.)
The MVB MServer property was formerly read-only at run-time. Now, you can set the MServer property before executing code.This gives you the ability to change servers from your application.
Visual M now includes a new VisM control for use with 32-bit Visual Basic 4.0. The VisM control combines the properties and control events of the MVB control with the call-back functionality of the M desktop control. This allows you to use one Visual M control instead of two for your applications.
In addition to the basic MVB properties and events, the VisM control includes a new method, Execute. Execute is a shortcut that allows you to execute a line of M code in a single line of Basic, Pascal, or C++ without having to set properties.
The SSVNs ^$ZMVBRUN and ^$ZMVBPROP are no longer available. Starting with Visual M Version 7.0, you can no longer use them in your applications.
Visual M now correctly understands multi-byte characters.