Am Freitag, den 04.01.2008, 22:19 +0100 schrieb Frank Schönheit - Sun Microsystems Germany: > > See this here, too, will investigate and fix. (Should I have mentioned I > > disabled all the macros outside of .odbs? Who needs them?) > > Seems this was caused by me faking the pre-installed Basic libraries, to > contain my sample basic code/dialog. > > If you want to fix this in your installation, copy the attached > script.xlc to <installation>/user/basic (and > <installation>/presets/basic), overwriting the existing file.
Ah yes, that did it. :) ... must be one of the causes for all those "don't edit this config file by hand"-signs. ;) Meanwhile I did use the m1 for pretty normal things, creating and filling tables, indexes, queries and forms. Anything went normally, no unusual behaviour. 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. Thank's so far, Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
