Access 97 bugs related to ActiveX controls
Article ID: SFKB0004
Last Reviewed:   August 18, 1997
Applies To:   SPEED Ferret 3.0  (SPEED Ferret for Access 97/VB5)

Issue

Our internal testing of SPEED Ferret uncovered a couple of minor problems in Access 97 that affect the operation of SPEED Ferret.


Problem 1

If a form is opened in Design view under program control, and the program then attempts to assign a new value to the Text property of a RichText control on the form, Access reports run-time error 387: Property cannot be set.

Manifestation: When you attempt to replace the Text property of a RichText control using SPEED Ferret, the replacement will fail and the Status field will display "Pending, can’t save: Property cannot be set".


Problem 2

If a form is opened in Design View under program control, and the program then attempts to assign a new value to the Font.Name property of a RichText, ListView, TreeView, TabStrip or StatusBar control, Access does not report an error. However, the new property value does not "stick". Instead, the original property value remains.

Manifestation: When you attempt to replace the FontName property of one of these controls using SPEED Ferret, the replacement will fail, but the Status field will display "Completed".


Workaround

You can set these properties manually. The bugs only surface when the properties are being set under program control.