MS Office macros not working in calc

[eu]

Binary package hint: openoffice.org

I use Open Office 3.1.1, build :9420 and have macros, running since 2001 and created in MS-Office.
They ran without problem in Ububtu 8.14, Ubuntu 9.10 but now, with the same Ubuntu 9.10 they either don't run,
report errors "35" ,subprocedure or function not defined.

In summary: No change in the program and now not longer working.

I created a bug report and hope this is attached. This time the macro stopped wothout any error and w/o any action.
Last time with copy/paste in another prg it worked. It's simple and should delete a defined number of rows in an spreadsheet to remove undesire data.

Many thanks for any hints.
best regards
Eugen

ProblemType: Bug
Architecture: amd64
Date: Sun Sep 26 19:30:27 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
Package: openoffice.org-core 1:3.1.1-5ubuntu1.2 [modified: var/lib/openoffice/basis3.1/program/services.rdb]
ProcEnviron:
 LANGUAGE=en_GB
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-22.65-generic
SourcePackage: openoffice.org
Uname: Linux 2.6.31-22-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2470): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2470): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2503): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2519): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox-bin:2585): GLib-WARNING **: g_set_prgname() called multiple times

[penalvch (penalvch)]

eu, thank you for reporting this bug and helping to make Ubuntu better. Could you please attach a file that demonstrates this problem?

[Launchpad Janitor (janitor)]

[Expired for openoffice.org (Ubuntu) because there has been no activity for 60 days.]

[penalvch (penalvch)]

eu, we are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!