I switched from IBX 4.52 to 4.62 : properties QInsert, QDelete... are no
longer public and my code does no longer compile.Is this definitive ?

It give me some flexibility to do custom UpdateRecord.

"RESO / Claude GUTH" <reso...@club-internet.fr> wrote in message
news:3b612999_2@dnews...

Jeff has been telling people (and still is) that these properties are not to
be used directly. They are now protected and you should change your code to
use the standard SelectSQL, UpdateSQL, DeleteSQL and ModifySQL properties.

Woody

Yes it is definitive.  Expect also that they won't be IBSQL variables in the
future too.

RESO / Claude GUTH wrote:

--
Jeff Overcash (TeamB)   I don't think there are any Russians
(Please do not email    And there ain't no Yanks
 me directly unless     Just corporate criminals
 asked.  Thank You)     Playing with tanks.  (Michael Been)

If those properties are protected you can use a hack class to access it:

type
    THackIBDataSet = class(TIBDataset)
    end;
...

    with THackIBDataSet(IBDataSet1) do
    begin
        QInsert ...
        ...
    end
...

Of course that if Jeff changes internal implementation of SelectSQL,
InsertSQL and so, this will not work.

--
Sergio Samayoa
Lgica Software
http://www.geocities.com/logicasw/

        Which he has been saying for months he *will* do.

        -Craig

--
Craig Stuntz (TeamB)       Senior Developer, Vertex Systems Corp.
Delphi/InterBase weblog:   http://delphi.weblogs.com
Use Borland servers; posts via others are not seen by TeamB.
For more info, see http://www.borland.com/newsgroups/genl_faqs.html

Thank you evry body for your advices.

Actually I changed my code.

I had also troubles in custom UpdateRecord setting UpdateAction := uaApplied
gives a compiler error type mismatch between TUpdateKing and TIBUpdateKind.
TIBUpdateAction(uaApplied) doesn't work so I set const ibuaApplied =
TIBUpdateAction(5) and UpdateAction := ibuaApplied.

RESO / Claude GUTH <reso...@club-internet.fr> a crit dans le message :
3b612999_2@dnews...

RESO / Claude GUTH wrote:

Force the proper scope when this happens.  IOW

UpdateAction := IBCustomDataset.uaApplied;

uaApplied is defined in both IBCustomDataset.pas and Db.pas.  Depending on your
uses clause ordering will be the scope the compiler tries to use.  You can
change the scope by prepending the unit name to the constant.

--
Jeff Overcash (TeamB)   I don't think there are any Russians
(Please do not email    And there ain't no Yanks
 me directly unless     Just corporate criminals
 asked.  Thank You)     Playing with tanks.  (Michael Been)