Spurious macro warnings

[Paul Hyett]

Having had to reinstall Excel 2003 a couple of days ago, I now get a
'disable macros' warning when I load up a couple of spreadsheets that
don't even have macros *in them*.

Yes, I could turn down the security level to avoid the message, but that
doesn't explain why I'm being warned about macroless spreadsheets?

 

[GS]

Having had to reinstall Excel 2003 a couple of days ago, I now get a

'disable macros' warning when I load up a couple of spreadsheets that
don't even have macros *in them*.

Yes, I could turn down the security level to avoid the message, but
that doesn't explain why I'm being warned about macroless
spreadsheets?

Make sure all code windows for those workbooks are empty. If there's
*anything* typed in them the alert is triggered! Make sure there are no
other modules (standard/class/forms) either so that the VBA project is
empty (except for "Microsoft Excel Objects")!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

 

[CellShocked]

Having had to reinstall Excel 2003 a couple of days ago, I now get a
'disable macros' warning when I load up a couple of spreadsheets that
don't even have macros *in them*.

Are there any links in them that reference external files?

Yes, I could turn down the security level to avoid the message, but that
doesn't explain why I'm being warned about macroless spreadsheets?

Probably a ploy to get you to upgrade to the newer release.

Which is better, BTW.

 

[Paul Hyett]

Are there any links in them that reference external files?

Not AFAIK.

Probably a ploy to get you to upgrade to the newer release.

Which is better, BTW.

No doubt, but there seems little point doing so on a slow PC.

 

[Puppet_Sock]

Having had to reinstall Excel 2003 a couple of days ago, I now get a
'disable macros' warning when I load up a couple of spreadsheets that
don't even have macros *in them*.

Yes, I could turn down the security level to avoid the message, but that
doesn't explain why I'm being warned about macroless spreadsheets?

I may be mistaken, but I seem to have experienced this with
workbooks that once had VB code in them, but no longer did.
That is, I had a workbook. I added VB code to it, and saved it.
Then later I completely removed all the VB code, deleting all
modules etc. Then I saved the workbook. It seemed to be
able to remember that it once had VB code, and to behave
(wrt security) as though it still did.

I'm not sure how to get around that. Possibly if you copied
all your worksheets to another workbook that had never had
any VB it might get around it, but I have not tried that.
Socks

 

[Paul Hyett]

I may be mistaken, but I seem to have experienced this with
workbooks that once had VB code in them, but no longer did.
That is, I had a workbook. I added VB code to it, and saved it.
Then later I completely removed all the VB code, deleting all
modules etc. Then I saved the workbook. It seemed to be
able to remember that it once had VB code, and to behave
(wrt security) as though it still did.

That's a distinct possibility with the sheets in question.

I'm not sure how to get around that. Possibly if you copied
all your worksheets to another workbook that had never had
any VB it might get around it, but I have not tried that.
Socks

Thanks - maybe someone else may have a work-around?

 

[GS]

I may be mistaken, but I seem to have experienced this with
workbooks that once had VB code in them, but no longer did.
That is, I had a workbook. I added VB code to it, and saved it.
Then later I completely removed all the VB code, deleting all
modules etc. Then I saved the workbook. It seemed to be
able to remember that it once had VB code, and to behave
(wrt security) as though it still did.

That's a distinct possibility with the sheets in question.

I'm not sure how to get around that. Possibly if you copied
all your worksheets to another workbook that had never had
any VB it might get around it, but I have not tried that.
Socks

Thanks - maybe someone else may have a work-around?[/QUOTE]

I reiterate my original suggestion! Go to each code window, keyboard
*Ctrl+A*, hit the delete key, save the file when all done.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

 

[Zaidy036]

I reiterate my original suggestion! Go to each code window, keyboard
*Ctrl+A*, hit the delete key, save the file when all done.

Open and "Save As" xls or xlsx NOT xml

 

[Paul Hyett]

I reiterate my original suggestion! Go to each code window, keyboard
*Ctrl+A*, hit the delete key, save the file when all done.

To be fair, you didn't actually mention the Ctrl-A thing...

 

[GS]

I reiterate my original suggestion! Go to each code window, keyboard
*Ctrl+A*, hit the delete key, save the file when all done.

To be fair, you didn't actually mention the Ctrl-A thing...[/QUOTE]

I didn't think I'd need to mention it since I -assumed- you'd know that
spaces aren't visible without surrounding characters.

*Ctrl+A* is a standard editor shortcut to SelectAll. Again, I -assumed-
you'd know that.

I apologize for these inappropriate assumptions!

Also, Zaidy036 raises a good point about SaveAs format but it doesn't
apply (per se) to xl2003 and earlier files. For xl2007 and later the
file format is an issue.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

 

[Paul Hyett]

I didn't think I'd need to mention it since I -assumed- you'd know that
spaces aren't visible without surrounding characters.

*Ctrl+A* is a standard editor shortcut to SelectAll. Again, I -assumed-
you'd know that.

I did, but lost the context.

In any case, it didn't seem to help.

I apologize for these inappropriate assumptions!

Also, Zaidy036 raises a good point about SaveAs format but it doesn't
apply (per se) to xl2003 and earlier files.

I'm using 2003...

 

[GS]

Can you upload one of the errant files so we can try to figure out if
it's a file problem or the Excel install?

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion