2010/5/16 kev <[email protected]>: > This has happened to me once before on an older version of Openoffice but it > just happened to me again in 3.2. > > So, say I have a Calc spreadsheet and write a few user functions in the > Basic module that is attached to the spreadsheet document. I switch between > the Basic window and the spreadsheet window in test/modify cycles. > Eventually I get everything working the way I want. I close the Basic > window, keep working in the spreadsheet (or not), and then when I'm done I > hit the Save button on the spreadsheet and close that window too. Done for > the night, shutdown the computer and all that. Next day I start up my > computer, open the spreadsheet and it is the way I left it, as expected. > > This time, as that time before, I open the spreadsheet and get a face full > of macro errors. After being forced to click through _all_ of them > (hundreds, btw), I open the Basic module and I find myself looking at the > code, as it existed, halfway through yesterday's editing. The rest is gone > like it never happened. Functions are incomplete or missing (the source of > the errors). > > I guess I am a bit puzzled by what is going on since I'm not even sure what > the correct procedure is when saving a document -- it is very ambiguous. Am > I supposed to save the Basic module separately by clicking on the Save icon > in the Basic window? If so, why does the document seem to save the macros > automatically most of the time, and why is there no warning whatsoever, when > closing either the Basic or Calc window, that the macros aren't saved? > Otherwise I would have to guess that this is a nasty bug that happens once > in a while where the Basic module does not get saved when the spreadsheet is > saved. But I'd appreciate clarification on this to minimize the chances of > it happening again.
Sorry for not having an answer to your question, but this happened to me too many times (not with 3.2 yet though, since I did no macro programming the last couple of months). To avoid this I usually save the macro as text now and then, using that other save button. That way I can always get my code back in vase this happens again. Maybe someone should file a bug report about this. Even if we didn't use the correct saving procedure, I would consider this a bug. If not a functional one so at least a UI bug. Johnny Rosenberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
