I want to make one thing clear, this to be considered dangerous and
unadvised by me. A stored procedure runs in the context of a transaction on
the server from which the UDF is invoked. I presume that you may also be
performing operations on the very record the array is going to be getting
manipulated (unless you have a dedicated table just for the arrays and link
them up).

Are you doing updates in the UDF or are you merely calling the
put_slice/get_slice routines?

The main concern is if within the UDF things are being committed and then
the transaction from which the UDF was invoked became rolled back you would
have a problem of data integrity errors.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Chris Hulsey" <chulsey@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, February 02, 2001 9:19 PM
Subject: Re: [IBO] C++ with IBObjects and Interbase UDF's


> Hello,
>
> A Special Thanks to Thomas, Helen, and Geoff for your great support in my
> efforts to make my C++ DLL work with the Interbase 6.0.1 UDF. Well after
> much effort I finally figured out the real culprit. It is the fact that I
> have a line of code in the top part of my C++ DLL source(refer to my first
> message):
>
> #pragma link "IB_Components"
>
> I am unsure as to his importance for the functionality of IBO at this
point.
> I do believe though that he probably was only intended for those that wish
> to use IBO in executables(*.exe) versus DLL. He may be necessary for only
> the form or presentation side of IBO. At this point I only want to have
IBO
> functionality from within my DLL for purposes of being called from stored
> procedures that process "arrays" for update.
>
> So I am going to forge ahead and see what happens!!!!
>
>
> Chris Hulsey
> Visible Changes, Inc.
> chris@...
>
>
>
>
>
>
>