Le mardi 05 avril 2005 à 16:28 +0200, Cyrille Moureaux a écrit : Hi,
> Has anyone encountered a hangup when performing a result modification > (write) from either a query or the table itself, and been forced to kill > OOo, though the change is taken into account in mySQL on the next start? > > See sql.log pasted below(*), is there also an OOo log (and if so where?). > > The rest of OOo base is terrific and close to Access, except regarding > response times for large databases. > I'll probably respond to the question on the French list too when I get around to it, but insofar as I'm concerned, the answer is yes, yes and yes. I have reported a number of bugs that cause OOo to segfault when writing or modifying a mysql db, even with the latest MyODBC installed. This was with m87. Some of these bugs have been corrected in later CWS that haven't yet been integrated into the developer releases. At the present time, OOo pre 2.0 and Mysql don't seem to want to play with each other very nicely. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
