Ugh! I agree with Ryan, however, I work in a support position and, earlier,
thought I could get away with JUST 2007.

I was wrong about that - so, a few days ago, I uninstalled Office2007,
installed 2003, then put 2007 back on.

That's when my macro recorder started doing the thing it's doing - which is
to say, putting "ugly" code in EITHER 2003 OR 2007 VBA.

When I uninstalled 2007, I ran CCleaner, but I did not thoroughly annhiliate
the previous installation of 2007. (As you know Uninstalls do not do exactly
that; sometimes that's a good thing, but mostly not!

If I go back and do uninstalls again, any advice on the best way to remove
the previous settings, which may be the cause of my displeasure!

As I write this reply, I now realize I did not uninstall my version of ASAP
Utilities. Hmmm . . .

Nonetheless, any advice . . .

"ryguy7272" wrote:

I used to have booth versions of Office too. Then, I had problems like you
describe and decided to get rid of 2003. Why do you need old technology?
2007 will do everything that 2003 does, and a whole lot more too.

--
Ryan---
If this information was helpful, please indicate this by clicking ''Yes''.


"Rich" wrote:

I have Office 2003 AND Office 2007 installed on my PC.

Now, when I record a keystroke macro to put some text into a cell and hit
enter, then go to the VBA Editor, the resultant macro is not what I'm used to
seeing. For instance to record putting some garbage in Cell a1, I get the
following:

ActiveCell FormulaR1C1 <= VB_VarUserMemIdasdfasdfVB_VarUserMemId
Range& VB_VarUserMemIdA3VB_VarUserMemId '+Select

When I attempt to run it, I receive a "Compile error: Invalid use of
peropery".

What do I need to change?

Thanks for any help.