Code to save workbook without macros

[Sheldon]

Hello -

I am awfully rusty in Excel. I currently am working in 2007.

I need to write code that will save an .xlsm workbook without the macros.

I also need code to save it to a particular file name and always that
particular file name, even though it's going to overwrite the file.

Any help will be most appreciated!

 

[RyanH]

Ummm, without macros? You would then need to move your mouse to the Save As
sub menu.

 

[Gord Dibben]

See Chip Pearson's site for module removal before saving.

http://www.cpearson.com/excel/vbe.aspx


Gord Dibben MS Excel MVP

 

[Ron de Bruin]

Save the workbook as xlsx and the macro's are gone

Application.DisplayAlerts = False
'Save code
Application.DisplayAlerts = True

 

[Gord Dibben]

Cool!!

I just gotta get me one of those Excel 2007's<g>


Gord

 

[Ron de Bruin]

Hi Gord

Start downloading it now from MSDN

 

[Sheldon]

Thanks for your replies!

I tried using Ron's code and it works beautifully, however, I now have
another problem. I am left in the xlsx document and my xlsm document has
"disappeared." When I try to open the xlsm document, the macros just fire
and I end up in the xlsx document, which would mean I would never be able to
Edit the xlsm document.

How can I fix this?

 

[Ron de Bruin]

One way is set security to medium if you want to edit the code
Say No to use macro's

 

[Sheldon]

Duh! Told you I was rusty.

Thanks so much!

 

[Gord Dibben]

I've already got several DVD's from MSDN subscriptions with 2007 so the
availability is not the roadblock.

I'll have to get you to email me the full instructions for setting up
Virtual PC with Windows XP and Office 2007<g>


Gord

 

[Ron de Bruin]

Hi Gord

How much memory do you have in your machine ?

 

[Gord Dibben]

512mb RAM

40GB free storage available on C: if that's what you mean.


Gord

 

[Dave Peterson]

I wouldn't do it, Gord. In fact, I'm not sure you can. You may need 512M for
just the virtual PC.

I had 1GB of RAM and when I set up VPC to use 512M for WinXP Pro and Vista Home
Premium, the both worked exceedingly slow.

I added 2GB (3GB total) and set up each of the VPCs to use 1.5M and they're not
too bad.

FYI, the WinXP Pro .vhd (virtual harddrive?) takes about 12GB. And the Vista
Home Premium is at 10GB.

 

[Ron de Bruin]

Dave is correct Gord

Upgrade your machine

 

[Gord Dibben]

Thanks Ron and Dave

That's the message I also get from lurking around the VirtualPC news group
for a while.


Gord

 

[Gary Keramidas]

in my opinion, don't do it unless you need more than 65000 rows or 256 columns.
vba code runs slower, the interface sucks and some code isn't compatible.

that's my opinion.

 

[sbitaxi]

I wouldn't do it, Gord.  In fact, I'm not sure you can.  You may need512M for
just the virtual PC.

I had 1GB of RAM and when I set up VPC to use 512M for WinXP Pro and Vista Home
Premium, the both worked exceedingly slow.

I added 2GB (3GB total) and set up each of the VPCs to use 1.5M and they're not
too bad.

FYI, the WinXP Pro .vhd (virtual harddrive?) takes about 12GB.  And theVista
Home Premium is at 10GB.

Dave/Gord - does that mean you two are using Macs? Why else would you
be running VPC? I'm primarily a Mac user and would love to be able to
use Excel at home with VBA. Even the VBA that comes with 2004 is
limited and 2008 is non-existent!


Steven

 

[Dave Peterson]

I use a WinXP Home pc.

When xl2007 arrived, I didn't want to install it on my pc (just too chicken).
Same thing with Vista.

So instead of breaking something that works <vbg>, I downloaded VPC from MS and
installed a couple of virtual pc's.

So I can experiment with xl2007 and with Vista knowing that there's nothing I
can do to really screw up my "real" pc.

I thought that there were a few of windows simulators that you could use with a
Mac.

A search of google came up with this list:
http://www.macwindows.com/emulator.html

 

[Dave Peterson]

ps. I've read some posts that say that MS is going to add VBA to the next
version of MacOffice. (I have no idea when that is.)

 

[sbitaxi]

ps.  I've read some posts that say that MS is going to add VBA to the next
version of MacOffice.  (I have no idea when that is.)

I'm hoping it's better than the last time. 2004 does run VBA but there
are enough limits to it that it isn't worth putting time into learning
how to convert PC macros for Mac Macros.