PRB: Error 419 Occurs if RecordSet is Assigned to Data Control
Article ID: 149041
Article Last Modified on 7/13/2004
APPLIES TO
- Microsoft Visual Basic 4.0 Standard Edition
- Microsoft Visual Basic 4.0 Professional Edition
- Microsoft Visual Basic 4.0 Professional Edition
- Microsoft Visual Basic 4.0 16-bit Enterprise Edition
- Microsoft Visual Basic 4.0 32-Bit Enterprise Edition
This article was previously published under Q149041
SUMMARY
Passing a Recordset object from a client to an OLE automation server (or
vice versa) is allowed. However, this Recordset object cannot subsequently
be assigned to a data control. Any attempt to do so results in error 419,
"Permission to use object denied."
CAUSE
Notifications for the IConnectionPoint interface are not currently
marshaled by OLE, so setting the Recordset property of a data control
to a Recordset object that was passed in from another process fails
at some point during initialization. All properties and methods of the
Recordset object can be utilized normally, so code can be written to
access the passed Recordset object and perform all desired DAO operations.
STATUS
This behavior is by design.
Additional query words: kbVBp kbdse kbDSupport kbVBp400
Keywords: kbprb KB149041