by madshi » Mon Feb 05, 2018 11:02 am
I received an email from Atozed in January with a modified madIWSupport.pas file. It worked fine for me, but with a little caveat (see below). I've now modified madIWSupport.pas to optionally either use my old hacked solution (which works for me with the latest IW version), or the official IW exception callback. You can choose by defining or undefining the "{$define useIWExceptionCallback}" at the top of madIWSupport.pas. See attached test project.
Here's the little caveat: When using IntraWeb's new exception callback, the test project produces a popup "ds1: Cannot perform this operation on a closed dataset". When using my dirty hook solution, this popup does not appear. To be honest, I'm not 100% sure if the average IW user would want this popup to appear or not. What do you think?
I've reported this caveat to Atozed, but haven't heard anything back.
- Attachments
-
iwprj1.zip
- (91.11 KiB) Downloaded 13 times