oole2.dll what does it do and can it be removed in Studio 5.2.3 (safely)

Doug Easterbrook doug at artsman.com
Fri Jun 10 08:56:45 EDT 2016


hi Kelly.

Thanks for the info …  it seems like it is probably safe to remove if you are using studio for server processes.


I know historically that omnis used to complain if omni2ui.dll was not present (which refers to oole2.dll)


Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug at artsman.com
http://www.artsman.com
Phone (403) 536-1205

> On Jun 10, 2016, at 1:00 AM, Kelly Burgess <kellyb at montana.com> wrote:
> 
> I see that developer note about the discontinued nature of the xcomp, with "Further information on the OLE2 component can be found in the Omnis Programming Manual."  but that link points to a current version of that manual, which omits this section:
> 
> --------  from Studio 5 Omnis Programming manual  ------
> 
> OLE Picture
> 
> The Windows implementation of OLE2 provides features such as Linking and embedding, and in place activation. Using the OLE Picture component you can link or embed many different types of object into your database, including spreadsheets, charts, pictures, and word processing documents.
> 
> < etc. >
> 
> - $getobject()
> returns an automation object (refer to the Automation section for further information on automation objects).
> For example
>                ; myObject is a variable defined as Object with no subtype
>                ; myOLEfield is an item reference for the OLE Picture field
>                Do myOLEObject.$getobject() Returns myObject
>                Ok Message {The name of the OLE objects server is [myOLEObject.$appname]}
> 
> - $doverb(constant)
> invokes the specified action on the OLE object and returns an HRESULT error code
> (refer to OLE Automation for further information concerning HRESULT error codes);
> the following constants are available
> 
>  kOLEPrimary	the default action for the object
>  kOLEShow		activates the object for editing; if the server application supports in-place activation,
> 				the object is activated in the OLE Picture field
>  kOLEOpen		opens the OLE object in a separate application window,
> 				even if the server application supports in-place activation
>  kOLEHide		causes the object to remove its user interface, toolbars, etc.,
> 				from the view; applies to in-place activated objects only
>  kOLEUIActivate	if the object supports in-place it is activated, otherwise an error occurs
>  kOLEDiscardUndoState	discards any undo state without deactivating the object
> 
> ----------------------------
> 
> Those are the methods and constants from my previous post.  So it seems like OLE Picture fields is what oole2.dll is all about, and it's probably a visual xcomp.
> 
> Kelly
> 
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com




More information about the omnisdev-en mailing list