I have used Excel since 1992, and I have never see this error message before. I'm now a new Office 2007 user, so I don't know what the problem is. I get the "Can't shift objects off sheet" error whenever I try to insert columns or rows.



The spreadsheet contains NO "objects" but it's an xlsm sheet because I have macros. The macros only select a range of cells, and them sort them various ways. Apparently Excel doesn't like me messing with the range AT ALL. The earlier versions of Excel had no problem - they just let an extra column drop off to the right, or an extra row drop off at the bottom and sorted everything else, so you had to modify your macros whenever you changed your range. And I'm prepared to do that.

But I apparently have to use an xlxs sheet (I'm still not clear on why we have different sheets in this version - macros work in .xlsx as well, and let me insert columns and rows). Or do I have to delete all my macros and start over any time I need to change the layout in xlsm format?

Why do I need xlsm format? Any reason?

Hi,
You can run macros on an xlsx file, but it can't contain macros itself.

This message has nothing to do with macros. Do you have any comments in the sheet (they may or may not be visible)?

If you can't find anything then you're welcome to attach the workbook to the thread for us to look at.

I deleted all the comments, and I still can't insert. It's still so new I haven't even added any formulas yet. The macros are the only thing in the worksheet that isn't straight text.

I ended up saving it as xlsx and inserting a column, then saving it back as xlsm. Please look and let me know if you have any thoughts.

Thanks!

Attached Files

Topic Status.xlsm (37.0 KB, 10 views)

Sorry. I forgot to disable the password. Here's a better file.

Attached Files

Topic Status1.xlsm (37.5 KB, 17 views)

Hi,

I just opened the workbook you attached in #4 and I don't get any error messages when I insert columns or rows.

Then if the issue is something on my computer, can you think of what might be conflicting with the xlsm format, and creating the problem? Like I said, saving it as xlxs is my workaround, but it doesn't seem like it gets to the root of the issue...