Scribd
Upload
297 views

Using OLE Columns in A DataWindow Object

You can create OLE columns in a DataWindow object to store and retrieve binary large object (blob) data from a database using an OLE server application like Microsoft Excel or Word. To do so, the database must support a blob data type and the DataWindow object must have a column of this type defined. Properties like the database table, blob column, and OLE server must then be set. Previewing the DataWindow allows viewing and editing blob data using the associated OLE application and updating the database with changes.

Uploaded by

Jhosef Quijana Martinez
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
297 views

Using OLE Columns in A DataWindow Object

You can create OLE columns in a DataWindow object to store and retrieve binary large object (blob) data from a database using an OLE server application like Microsoft Excel or Word. To do so, the database must support a blob data type and the DataWindow object must have a column of this type defined. Properties like the database table, blob column, and OLE server must then be set. Previewing the DataWindow allows viewing and editing blob data using the associated OLE application and updating the database with changes.

Uploaded by

Jhosef Quijana Martinez
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

Using OLE columns in a

DataWindow object
You can create OLE columns in a DataWindow object. An OLE column
allows you to:

Store blob (binary large-object) data, such as Excel worksheets


or Word for Windows documents, in the database
Retrieve blob data from a database into a DataWindow object
Use an OLE server application, such as Microsoft Excel or Word
for Windows, to modify the data
Store the modified data back in the database

You can modify the document in the server, then update the data in
the DataWindow object. When the database is updated, the OLE column,
which contains the modified document, is stored in the database.
Database support for OLE columns If your database supports a blob
data type, then you can implement OLE columns in a DataWindow object.
The name of the data type that supports blob data varies. For
information on which data types your DBMS supports, see your DBMS
documentation.

Creating an OLE column


This section describes how to create an OLE column in a DataWindow
object. The steps are illustrated using a table that you can create
in the Database painter. It must contain at least two columns, id and
object:

The id column is an integer and serves as the table's key.


The object column is a blob data type and contains OLE objects
associated with several OLE servers.

To create the database table:


1. In the Database painter, create a table to hold the blob
(binary large-object) data.
The table must have at least two columns: a key column and a
column with the blob data type. The actual data type you choose

depends on your DBMS. For example, in Adaptive Server Anywhere,


choose long binary as the data type for the blob column. For
information about data types, see your DBMS documentation.
2. Define the blob columns as allowing NULLs (this allows you to
store a row that doesn't contain a blob).

Adding a blob column to the DataWindow object


This procedure describes how to add a blob column to a DataWindow
object.
To add a blob column to a new DataWindow object:
1. Create a new DataWindow object.
2. Specify the table containing the blob as the data source for
the DataWindow object.
Be sure to include the key column in the data source. You
cannot include the blob column in the data source; if you try,
a message tells you that its data type requires the use of an
embedded SQL statement. You will add the blob column later in
the DataWindow painter workspace. (If you use Quick Select, the
blob column is not listed in the dialog box.)

3.

Select Insert>Control>OLE Database Blob and click where you


want the blob column in the Design view.
The Database Binary/Text Large Object dialog box displays:

Setting properties for the blob column


This procedure describes the properties you need to set for the blob
column.
To set properties for a blob column:

1. (Optional) Enter the client class in the Client Class box. The
default is DataWindow.
This value is used in some OLE server applications to build the
title that displays at the top of the server window.
2. (Optional) Enter the client name in the Client Name box. The
default is Untitled.
This value is used in some OLE server applications to build the
title that displays in the title bar of the server window.
3. In the Table box, select the database table that contains the
blob database column you want to place in the DataWindow
object.
The names of the columns in the selected table display in the
Large Binary/Text Columns listbox.
4. In the Large Binary/Text Columns box, select the column that
contains the blob data type from the list.
5. If necessary, change the default key clause in the Key Clause
box.
PowerBuilder uses the key clause to build the WHERE clause of
the SELECT statement used to retrieve and update the blob
column in the database. It can be any valid WHERE clause.
Use colon variables to specify DataWindow columns. For example,
if you enter this key clause:
id = :id

the WHERE clause will be:


WHERE id = :id

6. Identify the OLE server application by doing one of the


following:
o If you always want to open the same file in the OLE
server application, enter the name of the file in the
File Template box.

For example, to specify a particular Microsoft Word


document, enter the name of the DOC file. If the file is
not on the current path, enter the fully qualified name.

Use the Browse button to find the file If you do not


know the name of the file you want to use, click the
Browse button to display a list of available files.
Select the file you want from the resulting window.
If you do not want to open the same file each time,
select an OLE server application from the OLE Class:
Description dropdown listbox.
When the server doesn't match the OLE blob data If you
specify a server that doesn't match the OLE blob object
or if your database contains objects belonging to
different servers, the OLE mechanism can usually handle
the situation. It looks for the server specified in the
object and starts it instead of the server you specified.

7. Enter text or an expression that evaluates to a string in the


Client Name Expression box.
The server may use this expression in the title of the window
in the OLE server application. The expression you specify can
identify the current row in the DataWindow object.
Use an expression to make sure the name is unique Use an
expression to make sure the name is unique. For example, you
might enter the following expression to identify a document
(where ID is the integer key column):
"Document " + String(id)
8. Click OK.
PowerBuilder closes the dialog box. The blob column is
represented by a box labeled Blob in the Design view.
9. Save the DataWindow object.

Here is what a completed Definition page for a Blob object in a table


called ole looks like in the Properties view:

Making the blob column visible


If the blob column is invisible in the DataWindow object until you
activate the OLE server, you can make it easy to find the blob column
by adding a border to the object.
Previewing an OLE column
Before using the DataWindow object in an application, you should
preview it in the Preview view or in preview mode to see how it
works.
To preview an OLE column in preview mode:
1. Select File>Run/Preview from the menu bar and select the
DataWindow object.
2. Click the Insert Row button.
PowerBuilder adds a blank row.
3. In the blank row, enter a value in the key column.
4. Double-click the column that contains the blob data type.
The OLE server application starts and displays the file you
specified in the File Template box or an empty workspace if you
specified only the OLE server name.
5. Review the file in the OLE server application and make changes
if you want.
When you use an OLE column to access an OLE server application,
the server application adds an item to its File menu that
allows you to update the data in the server application and in
the client (the DataWindow object). The text of the menu item
depends on the OLE server application. In most applications, it
is Update.
6. Select the menu item in the OLE server that updates the OLE
client with the modifications.

In the example, you would select Update from the File menu in
Microsoft Word. The OLE server application sends the updated
information to the DataWindow object.
7. Close the file in the server application (typically by
selecting Close from the File menu).
8. To save the blob data in the database, click the Save Changes
button in the PainterBar.
The new row, including the key value and the blob, are stored
in the database.

Later, after you retrieve the rows from the database, you can view
and edit the blob by double-clicking it, which invokes the OLE server
application and opens the stored document. If you make changes and
then update the database, all the modified OLE columns are stored in
the database.

You might also like