Hi Marc, > ... must be one of the causes for all those "don't edit this config file > by hand"-signs. ;)
*g* Funnily, I can't remember having edited this file manually. I took it from some working version, but I really do now know why this version stripped all those lines from the file ... > Meanwhile I did use the m1 for pretty normal things, creating and > filling tables, indexes, queries and forms. Anything went normally, no > unusual behaviour. Fine. Not really surprising to me :), I didn't touch those. I mainly reworked some application and scripting framework parts (see the tasks list in the spec to get an impression), so I think errors might hide therein. > Only one observation makes me think: Using "shutdown compact" from the > SQL window lead to closing the session, no data was accessible after > running this command. IIRC that was different in the last release > version I tried (2.3.1). I think using that one anything worked without > re-opening the .odb file (that helped), but I'm not really sure what is > right and what's wrong: > > The ordinary user would be happy to have it's tables connected after > compacting the database. But in fact a SQL command named "shutdown" that > shuts down the database is doing what it is asked for. I don't think I touched anything in this area, but maybe there were other changes between 2.3.1 and m238 (which is what this milestone is based on). For the behaviour as such: For one, it's absolutely undefined at the moment how the UI should behave when you shut down via direct SQL. That said, I also tend to think the requirement to close and re-open the .odb makes sense. 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]
