Problem with Excel File after Upgrading to Office 2000

  • Thread starter Thread starter Melody Adell
  • Start date Start date
M

Melody Adell

A user has a spreadsheet that was in Excel 97 (that was
most likely done in Quattro Pro originally) that seems to
have macros in it. There were two shortcut key
assignments programmed in the spreadsheet (Cntrl + C and
Cntrl + L). The file worked fine in Excel 97, but when
the machine was upgraded to Excel 2000, the "shortcuts" no
longer work. Anyone have any idea?
 
A user has a spreadsheet that was in Excel 97 (that was
most likely done in Quattro Pro originally) that seems to
have macros in it. There were two shortcut key
assignments programmed in the spreadsheet (Cntrl + C and
Cntrl + L). The file worked fine in Excel 97, but when
the machine was upgraded to Excel 2000, the "shortcuts" no
longer work. Anyone have any idea?

Yes, rewrite the Quattro Pro macros in VBA. That and giving back Excel 97 to
this particular user are your only alternatives. Excel 97 was the last Excel
version that supports 123-like macros. Excel 2K and subsequent versions just
plain don't. Your IT department should have informed your users that this was
the case so that someone could have spent some time rewriting these macros
before migrating anyone from Excel 97 to 2K. Now you get to handle it damage
control style.

At the very least, the person who'll need to rewrite these macros in VBA will
need Excel 97 at least on a temporary basis in order to test for comparable
functionality (unless these were really simple macros).
 
I work in the IT department and after much digging around,
figured that our only alternative was that they'd have to
be re-written in VBA. Problem is, I cannot find
the "source code" for what the macros did from the start
to be able to rewrite them in VBA. Do you know how I can
find the "source code" behind the macro?
 
. . . Problem is, I cannot find
the "source code" for what the macros did from the start
to be able to rewrite them in VBA. Do you know how I can
find the "source code" behind the macro?

If a 123 or QP macro had been run with the [Ctrl]+A key combination, then it
must be in a range named \A. Press [F5], enter \A . That should take you to the
top cell in the macro range.
 
Harlan,

Thank you so much!

Melody
-----Original Message-----
. . . Problem is, I cannot find
the "source code" for what the macros did from the start
to be able to rewrite them in VBA. Do you know how I can
find the "source code" behind the macro?

If a 123 or QP macro had been run with the [Ctrl]+A key combination, then it
must be in a range named \A. Press [F5], enter \A . That should take you to the
top cell in the macro range.

--
Never attach files.
Snip unnecessary quoted text.
Never multipost (though crossposting is usually OK).
Don't change subject lines because it corrupts Google newsgroup archives.
.
 
I have a document that list equivalent Lotus 123 commands
to VBA. I'm looking for any information on Quattro Pro
macros. Do you know where I might find that kind of
information?
-----Original Message-----
. . . Problem is, I cannot find
the "source code" for what the macros did from the start
to be able to rewrite them in VBA. Do you know how I can
find the "source code" behind the macro?

If a 123 or QP macro had been run with the [Ctrl]+A key combination, then it
must be in a range named \A. Press [F5], enter \A . That should take you to the
top cell in the macro range.

--
Never attach files.
Snip unnecessary quoted text.
Never multipost (though crossposting is usually OK).
Don't change subject lines because it corrupts Google newsgroup archives.
.
 
Back
Top