AseConnection.InfoMessage only called once
In order to notify the user about the progress of a long operation i have set flushmessage on in the beginning of my batch and registered the InfoMessage callback, but it appears to be a design decision to collect all the messages and return them all at the end. So far it appears that I'm stuck with piping the output of isql or digging into the ct-library. Any plans to change this?
Mike Willett replied
We found the same thing a couple of years ago.
To get around this, we downloaded the Mono driver and made slight tweak to it - not difficult - to output the messages immediately.
We now use this for all our batch processes rather than the Sybase ADO drivers.