Thanks, Helen:

Couple of additional questions:
1. I understand the need to shutdown the database and on my development
computer, I'm using the full FB server.
I found the IBOAdmin component to do this--looks like IBOConfigService has the
Shutdown and ServiceStart procedures to do this. Is this correct?
2. Does all this apply for my end users who will be using FB embedded?

Thank you, again

Chuck Belanger

> IBO can't do any magic here to break the engine's rules!
>
> 1. Put the database into shutdown state using gfix or a Service Manager
> call (you'll need IBOAdmin components for this).
>
> 2. Perform the DROP CONSTRAINT and commit.
>
> 3. Perform the updates and deletes and commit.
>
> 4. Reinstate the constraint and commit.
>
> 5. Put the database back online using gfix or a Service Manager call.
>
> Note that any oversights in your handling of the relationships will cause
> failure at 4). You'll need to be prepared to catch exceptions at each step
> along the way.
>
> An effective way to pre-empt failure at 4) would be to perform the whole
> update and delete sequence inside a SP that includes exception handlers
> which will allow the process to skip over problem rows and log them out to
> an external log table. The external table will provide "hard" details of
> the problem relationships regardless of whether step 4 succeeds (and is
> committed) or fails (and is rolled back).
>
> Helen
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.17/228 - Release Date: 01/12/2006