There exists 2 ways to get this fields value.

1) One way is to stream the image to a file and then afterwards import it into the blob.



In this example I assume you already have the ADO Connection and thereby already got the ADORecordSet.

ADOStream.Type := 1; //1 = Binary
ADOStream.Open;
ADOStream.Write(ADORecordSet.Fields.Item(FieldName).Value);
ADOStream.SaveToFile('c:\tmp.bmp',2); //2 = SaveCreateOverWrite
ReturnTable.Picture.IMPORT('c:\tmp.bmp');
ADOStream.Close;
CLEAR(ADOStream);
 
Where ADOStream is 'Microsoft ActiveX Data Objects 2.8 Library'.Stream
and ADORecordSet is 'Microsoft ActiveX Data Objects 2.8 Library'.Recordset

FromRecSet := ADOConn.Execute('SELECT image FROM tableX','',0);
FromRecSet.MoveFirst;
 
//The following query is used to get a "blank" recordset, just like a INIT in Navision
MyQuery := 'SELECT [EntryNo], [Picture] FROM [MyTable] WHERE [EntryNo] = 0';
 
NewRecSet.Open(MyQuery,NAVconn,1,3,1);
NewRecSet.AddNew;
NewRecSet.Fields.Item('Picture').Value := FromRecSet.Fields.Item('image').Value;
NewRecSet.Update;
 

This is a detailed description for the used ADORecordSet command mentioned in the articles Stored Procedures and Navision and ADO in Navision.

ADORecordSet

The ADO RecordSet is defined by the automation ‘Microsoft ActiveX Data Objects Recordset 2.8 Library’.Recordset or by ‘Microsoft ActiveX Data Objects 2.8 Library’.Recordset

It is used to hold a set of records from a from a database table or a defined query. The Recordset object contains rows and columns (fields).

In the mentioned articles we are using the following ADORecordSet methods:

ADORecordset.ActiveConnection

Sets the definition for the current connection.

ADORecordSet.Close

Closes a RecordSet.

ADORecordSet.EOF

Returns true if the recordset is at the end of the buffered response (after the last record), otherwise it is false.

ADORecordSet.Fields.Item(‘Name’).Value

Returns a specific Items value. Fields are a collection of Items.

ADORecordSet.MoveFirst

Go to the first Record in the RecordSet.

ADORecordSet.MoveNext

Go the next record in the RecordSet.

ADORecordset.Open

Opens a connection to a database element, which gives access to records in a table, query results or saved recordsets.

ADOCommand

The ADO Command is defined by the automation ‘Microsoft ActiveX Data Objects 2.8 Library’.Command
It is used to execute a query against a database.

In the mentioned articles we are using the following ADOCommand methods:

ADOCommand.ActiveConnection

Sets the definition for the current connection.

ADOCommand.CommandText

The provider command. Is often either a sql query script or a stored procedure.

Sql query script example: ADOCommand.CommandText := ‘SELECT count(*) FROM [Customers]’;

Stored Procedure example: ADOCommand.CommandText := ‘[SP_CountCustomers]’;

ADOCommand.CommandType

The type of command, that is being executed with the CommandText.

Valid values are:

ADOCommand.CommandTimeout

No. of seconds to wait while trying to execute a command.

ADOCommand.CreateParameter

Creates a Parameter object. Is often used when calling Stored Procedures, where parameters are required.It takes the parameters name, type, direction, size and value.

• name is the name of the parameter object
• type specifies the data type for the object
• direction defines the direction of the parameter – in or out
• size specifies the length of a variable data type
• value is value of the parameter object

Example on types are:

• adBoolean (11) – indicates an boolean value
• adBSTR (8) – indicates a null-terminated character string
• adDate (7) – indicates a date value
• adDecimal (14)
• ad Numeric (131)

The complete list can be seen here.

ADOCommand.Execute

Executes the query, sql statement or procedure stated in the CommandText

ADOCommand.Parameters.Append(ADOParameter);

Appends the parameters created by the CreateParameter command.

Parameters contains all the parameters of a command object.

I have been asked to describe the different ADO commands parameters more explicit. So here are a detailed description for the used ADOconnection command in the articles Stored Procedures and Navision and ADO in Navision.

ADOconnection

ADOconnection is defined by the automation ‘Microsoft ActiveX Data Objects 2.8 Library’.Connection
It is used to create and open a connection to a data source (database).

In the mentioned articles we are using the following ADOconnection methods:

ADOconnection.Close

Closes a connection

ADOConnection.ConnectionString

Sets the details used for making a connection. It includes information about provider, server, database, userid and password.
Ex. 'PROVIDER=SQLOLEDB;SERVER=SQLServer;DATABASE=SQLDatabase;UID=SQLUserID;PWD=SQLPwd'

ADOConnection.Execute

Executes a query statement or a procedure. It takes the parameters commandtext, recordsaffected and option.

• Commandtext is a sql query statement or a call to a stored procedure.
• Recordsaffected returns the no. of records affected by the query.
• Option is used to set how the provider should evaluate the commandtext parameters.

Valid option values are:

ADOConnection.Open

Opens a connection. If connectionsstring is not set, it can be used in the open command as a paramenter.

Stored Procedures is a collection of SQL statements.

There are 2 ways to create a store procedure:

1. In the SQL Server Management Studio – you can right click on Stored Procedures and chose to create a new Stored Procedure. It will then create a template for you, which you just have to fill out and execute
2. The second way is to build a script by yourself

A script to create a Stored Procedure could look like this:

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
– =============================================
– Author: Ingrid Byllemos
– Create date:
– Description: Test of SP
– =============================================
CREATE PROCEDURE Count_Calls
– Add the parameters for the stored procedure here
@FromDate DateTime,
@ToDate DateTime
AS
BEGIN
– SET NOCOUNT ON added to prevent extra result sets from
– interfering with SELECT statements.
SET NOCOUNT ON;

– Insert statements for procedure here
SELECT COUNT(*) FROM [Call]
WHERE [Start Date] BETWEEN @FromDate and @ToDate

END
GO

When the script first is created, then simply execute it and a stored procedure is created on the SQL server.

Let us now take a look on how to use the stored procedure from Navision. Here we will be using ADO as described in an earlier article.

It is a bit difference from earlier described. First you have to open the connection to the SQL server:

CREATE(ADOConnection);

ConnectionString := 'PROVIDER=SQLOLEDB;SERVER=SQLServer;DATABASE=SQLDatabase;'+
………..'UID=SQLUserID;PWD=SQLPwd';
ADOConnection.ConnectionString(ConnectionString);
ADOConnection.Open;

This you should already have known how to do. Now we have to setup and open a ADO Command.

First we create the ADO Command and sets the ActiveConnection. Notice we use a Variant to transfer the connection from ADOConnection to ADOCommand.

CREATE(ADOCommand);

ActiveConnection := ADOConnection;
//ActiveConnection is type Variant

ADOCommand.ActiveConnection := ActiveConnection;

Next we have to setup the actual stored procedure, which has to be executed:

ADOCommand.CommandText := ‘[Count_Calls]‘;
ADOCommand.CommandType := 4;
ADOCommand.CommandTimeout := 0;

And the add Parameters to the command:

ADOParameter := ADOCommand.CreateParameter(‘@FromDate’,7,1,0,’05-01-2007′);
ADOCommand.Parameters.Append(ADOParameter);

ADOParameter := ADOCommand.CreateParameter(‘@ToDate’,7,1,0,’13-01-2007′);
//(name = @ToDate,type = 7 (date), direction = 1 (in), size = 0 (default), value = ’13-01-2007′)

ADOCommand.Parameters.Append(ADOParameter);

Notice we are using CreateParameter to add the parameters to the command.

Now execute the command and fetch the query result into a recordset:

ADOCommand.Execute;

CREATE(ADORecordset);
ADORecordset.ActiveConnection := ADOConnection;
ADORecordset.Open(ADOCommand);
ADORecordset.MoveFirst;

MESSAGE(FORMAT(ADORecordset.Fields.Item(0).Value));

Finally close the connection:

ADORecordset.Close;
ADOConnection.Close;
CLEAR(ADOConnection);

In the example we have been using the following automations:

• ‘Microsoft ActiveX Data Objects 2.8 Library’.Connection
• ‘Microsoft ActiveX Data Objects 2.8 Library’.Command
• ‘Microsoft ActiveX Data Objects 2.8 Library’.Parameter
• ‘Microsoft ActiveX Data Objects Recordset 2.8 Library’.Recordset

To use ADO in Navision, you have to use the automation “Microsoft ActiveX Data Objects 2.8 Library”

Lets take a closer on how to make a SQL connection and perform a SQL Query in Navision.

First you have to make a connection to the SQL Server:

ConnectionString := 'PROVIDER=SQLOLEDB;SERVER=SQLServer;DATABASE=SQLDatabase;UID=SQLUserID;PWD=SQLPwd';
 
ADOConnection.ConnectionString(ConnectionString);
ADOConnection.Open;
 
where ADOConnection is defined as 'Microsoft ActiveX Data Objects 2.8 Library'.Connection

Now you have a open connection to the SQL Server and are ready to execute scripts.

    
SQLString := 'SELECT [Name],[Customer No_] as CustomerNo ' +
             'FROM [Customer] WHERE [Customer No_] < 100';
 
ADORecordSet := ADOConnection.Execute(SQLString,RecordsAffected,RSOption);
 

Where ADORecordSet is defined as “Microsoft ActiveX Data Objects 2.8 Library’.Recordset”, RecordsAffected returns the number of records fetched and RSOption sets how the provider should evaluate the commandtext parameter (SQLString).

Now that the query has been performed, the query result is returned into a the ADO RecordSet. Which now can be parsed.

ADORecordSet.MoveFirst;
REPEAT
   TmpTable.Name := ADORecordSet.Fields.Item('Name').Value;
   TmpTable."No." := ADORecordSet.Fields.Item('CustomerNo').Value;
   TmpTable.INSERT;
   ADORecordSet.MoveNext;
UNTIL ADORecordSet.EOF;

When you are done using the ADORecordSet and the ADOconnetion, you have to close them:

ADORecordSet.Close;
ADOconnection.Close;