Hi Ariel, >> RESULT: the constructor returns an XCopyTableWizard reference, but >> XExecutableDialog.execute() makes OOo crash (without crash report -- at >> least here in Linux) > > It does here, too :(
That'd be fixed. In some sense, it *was* the wizard: It used the file driver in a way it had never been used before ... :-\ An instead of throwing an exception, the driver just crashed. Thanks for finding this. In the course of the fix, I also changed the behaviour to what you suggested: Invalid tables are noticed at creation time. That's not really my ideal solution, but ... We're talking about an UNO *wrapper* here. The wrapped code would need some more re-factoring to be able to properly propagate this error to the caller, so I decided to stay, for the moment, with checking the table beforehand. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
