On Sun, 27 Jul 2008 15:20:26 -0400 Julian <[EMAIL PROTECTED]> wrote: > I then tell my students that only by altering the coding > (what was written in the macro) to comply with the Macro > language used, can that Macro be ported. The end result > will be a Macro written in the different language.
On Sun, 27 Jul 2008 17:39:49 -0400 Anthony Chilco <[EMAIL PROTECTED]> wrote: > Hi Jerry, > As long as the macros use plain VB code without any Excel specific functions > or > variables, they should run in OOo v3. I haven't had much luck, though. I've > found that the OOo VB implementation will choke on stuff like this: > > Dim LastUsedRow As Integer > Dim LastUsedCol As Integer > > ActiveCell.SpecialCells(xlLastCell).Select > LastUsedRow = ActiveCell.Row > LastUsedCol = ActiveCell.Column Thanks Julian and Antony. In my research I found a coupleof helpful sites: This is on the OO.o site. http://documentation.openoffice.org/HOW_TO/various_topics/VbaStarBasicXref.pdf This is a converter. http://www.business-spreadsheets.com/vba2oo.asp Fortunately the new Financial Engineer who is rewriting the spreadsheet has agreed to maintain it both as OO.o Calc as well as Excel. Not sure if we will be using OO.o 2.4.1 or 3.0 but we will update to 3.0 when it is officially released. -- Jerry Feldman <[EMAIL PROTECTED]> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
signature.asc
Description: PGP signature
