Hi Andrew, > Turns out that Base had not quoted the name of the aliased column > that I created using the max funtion in the first view. This didn't > seem to bother the engine while it was running, but when it went to > startup again and was reading the script file this caused a column > not found error.
Ouch. > I can attach a copy of the corrupted database to an issue. Question is > should I limit to just this scenario or make it broader. For example I > have found 2 or 3 ways to make this type of thing happen. If "this type of thing" boils down to "views with column aliases are wrongly stored in the script file", then it's one issue only. If "this type of thing" manifests in similar ways in the UI, but under the hood looks different (say, in another scenario the script file is correct, but something else is wrong), then it's a different issue. If you can't tell those cases apart, or are otherwise in doubt, submit multiple issues. Thanks & Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
