dbansal,
IMHO it is not a good idea to change a driver, because:
* A good driver is tested and released. Any changes remove this status and require a new testing and release procedure.
* Not all drivers are fully documented for their internal workflow.
Changing some internals may break this workflow or introduce bugs.
* It will probably require _some_ extra time to understand the existing driver.
...
Add your functionality into a wrapper to the existing driver instaed.
Put its main into a new BD and copy all of its controls and displays
to your wrapper's FP. Connect 'em.. Create a while with shift registers
or even better a state machine that keeps the actual state of the
called driver and saves/reads this state to/from your external file (in
your case your excel sheet). You may either add a new control that
allows to save the existing state, do this saving after each
successfull call to the existing driver or whatever rule you need and
implement.
Jusdt my Euro 0.02...
Greetings from Germany!<br>-- <br>Uwe