Hi Helen

> Well, the place to start would be to look at the code where you pick up the text from the current IBODataset row to pass it to the ADOQuery parameter. Of special interest would be whether you are relying on some record number property that isn't valid for an IBO set...or where you might be treating null and empty string somewhere as though they were equivalent.
>
>

There is no code copying between the two! The IBOQuery result fields
have the same as the parameters in the TADOQuery. The TADOQuery is set
to use the TIBOQuery as the .Datasource. Sorry I should have been clearer.

After loading master and source (IBO AND ADO respectively) SQL
statements from a script. I loop through something like

IBOQuery.first;
while (IBOQuery.Eof = False) do begin
ADOQuery.ExecSQL;

IBOQuery.Next;
end;

I thought the problem was with the ADO Query but I put a break point on
before the .ExecSQL and used the 'Evaluate/Modify' tool in Delphi to
view the data in the IBOQuery at that point.
FieldByName('Stock0015').AsString <> '' but
FieldByName('Stock0015').IsNull = True !

Sorry about using Delphi syntax for those non Delphi people.


Hope that makes the problem clearer.



Rob Martin
Software Engineer

phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com

Wild Software Ltd