PRA: Open OLE Objects Not Saved When Record Changes (2.0)Article ID: Q103136Creation Date: 18-AUG-1993 Revision Date: 19-SEP-1996
The information in this article applies to:
SYMPTOMS
Advanced: Requires expert coding, interoperability, and multiuser skills.
If you are editing an OLE object that is opened from an OLE field, and
you then move to a different record, there is no indication that the
record was changed. The OLE object in the OLE server is closed and all
changes to the object are lost.
RESOLUTION
In Version 1.0
One way to work around this problem in Microsoft Access version 1.0 is
to call an Access Basic function in the OnExit property of the object.
The function prompts you to verify that the object has been
updated. The following is an example of this function:
A_ObjectUpdate
End If
End Function
Every time you pass through the OLE field, the function will be run
and the dialog box will be displayed. Unfortunately, there is no way to
test
whether or not the object has been edited.
In Versions 1.1 and 2.0 In Microsoft Access versions 1.1 and 2.0, a dialog box appears, indicating that the object is editable and gives you the option to update the object before moving on to the next record. For example, the following message appears after you open one of the pictures in the Employees table in the sample database NWIND.MDB:
The object "Paintbrush Picture" is open for editing and may have been modified. Update before saving? Yes, No, Cancel or HelpMORE INFORMATION
Steps to Reproduce Problem
list, Paintbrush is no longer available. If you go back to the recordyou were editing, the picture will not contain the changes you made. |
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.