ACC1x: Setting OLE Object Property May Cause GP FaultID: Q96893
|
Microsoft Access will produce a general protection (GP) fault if the OLEDATA property is set to a null value or an invalid object.
OLEDATA is a property of an unbound embedded object used in either
a form or report. The property is not available in the Object
Properties dialog box; it is set by Microsoft Access and can only
be modified using Access Basic code.
If the OLEDATA property is set to an invalid object, Microsoft
Access will display the error "Not a valid OLE object." Microsoft
Access will allow you to exit the dialog box and continue to work
in design mode. The frame will remain in the form or report;
however, since its link is broken, it will be dimmed. Access will
produce a GP fault when leaving design mode to display the form in
view mode, or the report in print preview mode.
If the OLEDATA property is set to null, Microsoft Access will display the
error "The setting you entered isn't valid for this property" and produce
a GP fault upon exiting the dialog box.
Setting the embedded objects Visible property to False will suppress the display of the object.
Microsoft has confirmed this to be a problem in Microsoft Access version 1.0. This problem was corrected in Microsoft Access version 1.1.
Any unbound embedded object inserted with the Paste, Paste Link*, or Paste Special* command is subject to the GP fault if the OLEDATA property is set to a invalid object.
The setting you entered isn't valid for this property.
Not a valid OLE object
Keywords : kbole kbprg IntpOle
Version : 1.0
Platform : WINDOWS
Issue type : kbbug
Last Reviewed: March 20, 1999