Hello Jerry,
You wrote:
At work, we have a spreadsheet that serves as a specification for the
C++ product that I am working on. The previous maintainer of the spec
implemented the math as forulae, and was very compatible with OO.o. I
work exclusively on Linux, and I need the spec in OO.o. The new
maintainer of the spec wants to convert this to be macro based (which
is better than the old spec for a number of reasons), but he wants to
maintain it in Excel because he knows VBA, and the spec will be sent
out to other people within the company and to some customers. While we
have agreed that he will also maintain an OO.o document, I was
wondering if there is a good document that compares OO.o basic to VBA.
My premise at work is that the document must be available as an OO.o
document because Excel does not run under Linux.
I may be able to help, though you may not like what I
shall state.
I am an Adjunct Lecturer for the Mathematics & Computer
Science Department. I have been teaching SpreadSheet
Analysis for the past ten years. I have students who have
to work with various brands of electronic spreadsheet
packages (Lotus, Excel, Visicalc, ProCalc, and brands and
versions which run on all sorts of computers and computer
operating systems. MS Excel is currently the package used
at the college (run with the MS Win system -- currently XP).
One of the things I teach is Macros. One of the things
I also tell my students is that it is up to the manufacturer
of the electronic spreadsheet package to decide which
programming language should and will be used to create
Macros to control the outcome of things about and in a
workbook. I tell them that even though the source code (the
wording and manner of setting it up) may look the same or
very similar to each other, there can be major differences
in the final results, based on which programming language
that coding was written. Thus, a Macro written with SQL
will not work with a workbook which is opened into a package
which uses Rexx as the programming language for Macros; and,
similarly, a Macro written in MS VBA will not work with a
workbook which is opened into a package which does not use
MS VBA as the Macro language.
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.
Again, hope this helps.
Regards,
Julian.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
