Remove whitespace in VBA excel

calendar_today Asked May 13, 2012
thumb_up 11 upvotes
history Updated April 14, 2026

Direct Answer

You should be using CStr not Str Then no workaround is needed for removing an unncessary space ie f = "F" & CStr(toIndex) g = "G" & CStr(startIndex) From Excel help for…. This is a 3-line VBA Core snippet, ranked #77th of 95 by community upvote score, from 2012.


The Problem (Q-score 1, ranked #77th of 95 in the VBA Core archive)

The scenario as originally posted in 2012

I have some code for move text from cell to cell

Dim startIndex As Integer
Dim toIndex As Integer
Dim f As String
Dim g As String

For startIndex = 50 To 60 Step 2
toIndex = Str(startIndex + 1)
f = "F" & Str(toIndex)
g = "G" & Str(startIndex)
Range(f).Value = Range(g).Value
Range(g).Value = ""
Next startIndex

But variable f has “F 51” value instead of “F51”.

How solve this problem ?
p.s. It’s my first code on vba.

Why community consensus is tight on this one

Across 95 VBA Core entries in the archive, the accepted answer here holds solid answer (above median) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — solid answer (above median) (+11)

3-line VBA Core pattern (copy-ready)

You should be using
CStr
not
Str

Then no workaround is needed for removing an unncessary space

ie

 f = "F" & CStr(toIndex)
 g = "G" & CStr(startIndex)  

From Excel help for Str

When numbers are converted to strings, a leading space is always reserved for the sign of number.


When to Use It — vintage (14+ years old, pre-2013)

Ranked #77th in its category — specialized fit

This pattern sits in the 91% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the VBA Core archive for a higher-consensus alternative.

What changed between 2012 and 2026

The answer is 14 years old. The VBA Core object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

Is this above-median answer still worth copying?
expand_more

Answer score +11 vs the VBA Core archive median ~4; this entry is solid. The score plus 1 supporting upvotes on the question itself (+1) means the asker and 10 subsequent voters all validated the approach.

Does the 3-line snippet run as-is in Office 2026?
expand_more

Yes. The 3-line pattern compiles on Office 365, Office 2024, and Office LTSC 2026. Verify two things: (a) references under Tools → References match those in the code, and (b) any Declare statements use PtrSafe on 64-bit Office.

This answer is 14 years old. Is it still relevant in 2026?
expand_more

Published 2012, which is 14 year(s) before today’s Office 2026 build. The VBA Core object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which VBA Core pattern ranks just above this one at #76?
expand_more

The pattern one rank above is “Reference excel worksheet by name?”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 1, Answer-score 11, original post 2012, ranked #77th of 95 in the VBA Core archive. Last regenerated April 14, 2026.

vba