Columns("A:A").Select gives error...

[DhavokD]

Run-time error '1004':

Application-defined or object-defined error.


-----------------------------------------------------

I have one main macro that creates new workbooks, puts data in them based on at text file, then formats them how they need to be (Cell data format, coloring, spacing, etc). For some reason Columns("A:A").Select gives me an error. Is this because I am creating a workbook from code? If so, how do I make it work?

[Phil_V]

It sounds more like a coding error, but to know that we would need to see the code....

[shg]

There's nothing wrong with the syntax -- depends on the context, I guess.

[DhavokD]

Fix:

Worksheets(1).Columns("A:A").Select

...

weird.

[shg]

Methinks the worksheet is hidden. You can't select something on a hidden worksheet.

[romperstomper]

If your code is in a worksheet module, then an unqualified reference to Columns("A:A") would always refer to that sheet. If that sheet isn't the active one, you can't select a range on it. Specifying the sheet, assuming Worksheets(1) is active, cures the problem.

[Phil_V]

...and this is why it is usually helpful if the OP posts more than just a single fraction of code when having a problem

[RayInAZ]

I had an issue selecting a column, via VBA, when one of the rows was merged.
In my case it was row 1, not sure if that played a role or not.
VBA insisted on selecting multiple columns for Columns("A:A").Select.
Screwed around a while to find this issue.

[jolivanes]

@RayInAZ
When you merge cells, you risk:
Losing the ability to properly sort data.
Losing the ability to run VBA programming code on your data because it doesn't handle merged cells very well, and a significantly larger amount of code may need to be written to cover the merged cells.
and
https://edu.gcfglobal.org/en/excel-t...rging-cells/1/