Julian wrote:
Hello Anthony,
Anthony Chilco 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
The assignments to lastused row and col work, but xlLastCell isn't
there. I don't know if there's a method to accomplish this that will
work in both packages.
tc
Jerry Feldman 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 know and have used several programming languages, including more
than one form of BASIC. One of the reasons a past client of mine asked
for my help was because I am able to translate the source code from one
BASIC to another. At that time it was being able to translate AppleSoft
(a Microsoft product) BASIC to an extended BASIC (also written by
Microsoft, but designed for the Spectrovideo 328 computer). If one
tried running the program on the Spectravideo computer, as it was
written in AppleSoft, it would finally fail because the interpreter
would not know what to do. The basic set up was the same, but certain
types of system calls were totally different or not needed when
programming for the Spectravideo computer.
If you or Jerry wish to have the Macros work under OpenOffice, you
MUST translate, by hand, that code which is different. How do you do
that? You do that by first having a good idea of how one of those
structured BASICs work, and by having a manual for each one in front of
you. Then, you go over each line of code, carefully making sure what is
written will operate in the same way. If it will not operate in the
same way, or will not operate at all, you must know how to change it and
with what to change it.
This is painstaking work. I wish I knew an easier and faster way,
but I do not. But it can be done and done quite successfully.
BTW, you might want to have a look at the original developers of
structured BASIC. It is called, "True BASIC." It will give you some
insight about all the brands of structured BASIC.
Hope this helps.
Regards,
Julian.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Julian,
I'm aware of the problems of trying to run the same code with different
interpreters. I think you're missing an important point, though. V3 of OOo has
introduced MS VBA compatibility as a new feature. It's there for the plain
vanilla code, but not yet complete.
tc
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
