File attached
Printable View
File attached
I actually had a use for this a couple of days ago, Malcolm. I was actually trying to get the column letters in the worksheets and ended up using the CODE and CHAR functions to work out where I needed to be.
i.e. =CHAR(COLUMN()+64)
The above only works up to Column Z, of course, then you have to fool with it again. I like your method better. :)
:banghead: How simple you make that look!! I went the long way around to get the integers. :banghead::banghead::banghead:
I was answering a question for someone on another forum the other day. The OP was going in all sorts of directions, but the long and short of the situation was that they were retrieving data and pasting it into a worksheet range that may or may not be the same every time.
I farted around with a couple of functions that the OP seemed to be elated with. In any case, here is the code and an example workbook to play with for anyone interested.
The Test It button simply gets a random range for me to test the functions with. I left it in for the OP to be able to see if it was going to fit the purpose he needed.Code:Option Explicit
Sub Test()
Dim Reply As String
Dim Temp As Range
Dim TheCell As Range
Dim FinalAnswer As String
Randomize
Set TheCell = Cells(4, Range("MyRandom"))
Set Temp = Range(TheCell, TheCell.Offset(0, Range("MyRandom").Value))
Temp.Select
Reply = Temp.Address
FinalAnswer = ParseAddy(Reply, False)
FinalAnswer = ParseAddy(Reply, True)
Calculate
End Sub
Public Function AlphaDec(AlDec As String) As Double
' Designed to work for base 26 alphabet numbering system like Excel Column names
Dim i As Long
Dim j As Variant
Dim k As Long
Dim n As Long
Dim AlphaDecArray() As Double
n = Len(AlDec)
k = -1
ReDim AlphaDecArray(1 To n)
For i = n To 1 Step -1
j = Mid(AlDec, i, 1)
k = k + 1
Select Case j
Case Is = "A"
AlphaDecArray(i) = 1 * 26 ^ (k)
Case Is = "B"
AlphaDecArray(i) = 2 * 26 ^ (k)
Case Is = "C"
AlphaDecArray(i) = 3 * 26 ^ (k)
Case Is = "D"
AlphaDecArray(i) = 4 * 26 ^ (k)
Case Is = "E"
AlphaDecArray(i) = 5 * 26 ^ (k)
Case Is = "F"
AlphaDecArray(i) = 6 * 26 ^ (k)
Case Is = "G"
AlphaDecArray(i) = 7 * 26 ^ (k)
Case Is = "H"
AlphaDecArray(i) = 8 * 26 ^ (k)
Case Is = "I"
AlphaDecArray(i) = 9 * 26 ^ (k)
Case Is = "J"
AlphaDecArray(i) = 10 * 26 ^ (k)
Case Is = "K"
AlphaDecArray(i) = 11 * 26 ^ (k)
Case Is = "L"
AlphaDecArray(i) = 12 * 26 ^ (k)
Case Is = "M"
AlphaDecArray(i) = 13 * 26 ^ (k)
Case Is = "N"
AlphaDecArray(i) = 14 * 26 ^ (k)
Case Is = "O"
AlphaDecArray(i) = 15 * 26 ^ (k)
Case Is = "P"
AlphaDecArray(i) = 16 * 26 ^ (k)
Case Is = "Q"
AlphaDecArray(i) = 17 * 26 ^ (k)
Case Is = "R"
AlphaDecArray(i) = 18 * 26 ^ (k)
Case Is = "S"
AlphaDecArray(i) = 19 * 26 ^ (k)
Case Is = "T"
AlphaDecArray(i) = 20 * 26 ^ (k)
Case Is = "U"
AlphaDecArray(i) = 21 * 26 ^ (k)
Case Is = "V"
AlphaDecArray(i) = 22 * 26 ^ (k)
Case Is = "W"
AlphaDecArray(i) = 23 * 26 ^ (k)
Case Is = "X"
AlphaDecArray(i) = 24 * 26 ^ (k)
Case Is = "Y"
AlphaDecArray(i) = 25 * 26 ^ (k)
Case Is = "Z"
AlphaDecArray(i) = 26 * 26 ^ (k)
End Select
Next i
AlphaDec = Application.WorksheetFunction.Sum(AlphaDecArray)
End Function
Public Function ParseAddy(MyAddy As String, LeftOrRight As Boolean) As Integer
' If Left Argument is true, returns MyLefty,
' If Left Argument is false, returns MyRighty
Dim MyLefty As String
Dim MyRighty As String
Dim NewLefty As Integer
Dim NewRighty As Integer
Dim TheColon As Integer
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "$", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "1", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "2", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "3", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "4", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "5", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "6", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "7", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "8", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "9", "")
MyAddy = Application.WorksheetFunction.Substitute(MyAddy, "0", "")
TheColon = Application.WorksheetFunction.Find(":", MyAddy)
' MsgBox ("The Colon is in position #" & TheColon)
MyLefty = Left(MyAddy, TheColon - 1)
MyRighty = Right(MyAddy, Len(MyAddy) - TheColon)
Select Case LeftOrRight
Case Is = True Or 1
NewLefty = AlphaDec(MyLefty)
ParseAddy = NewLefty
Case Is = False Or 0
NewRighty = AlphaDec(MyRighty)
ParseAddy = NewRighty
End Select
MsgBox (NewLefty & " " & NewRighty)
End Function
Regards,
How about thisQuote:
Originally Posted by Ken Puls
=LEFT(ADDRESS(ROW(),COLUMN(),2),FIND("$",ADDRESS(ROW(),COLUMN(),2),1)-1)
This is what I use in VBA
[vba]
'-----------------------------------------------------------------
Function ColumnLetter(Col As Long)
'-----------------------------------------------------------------
Dim sColumn As String
On Error Resume Next
sColumn = Split(Columns(Col).Address(, False), ":")(1)
On Error GoTo 0
ColumnLetter = sColumn
End Function
[/vba]
This is actually Cyberdudes code from a potential KB item, posted here for him to access.
Regards
MD
I use this in Access to convert field names that represent cell addresses for transferring carefull crafted queries into reporting templates. http://vbaexpress.com/kb/getarticle.php?kb_id=838
[vba]Public Function GetRowColumn(strRowColumn) As RowColumn
Dim lngCount As Long
Dim lngChar As String
'function to get cell references out of column names where the column names
' are equivalent to A1 style cell references (Note:R1C1 references won't work with this)
For lngCount = 1 To Len(strRowColumn)
lngChar = Asc(Mid(strRowColumn, lngCount, 1))
If lngChar >= Asc("0") And lngChar <= Asc("9") Then
Exit For
End If
Next lngCount
'this extracts the column and row from the Field Name in the recordset.
GetRowColumn.col = Left(strRowColumn, lngCount - 1)
GetRowColumn.row = Right(strRowColumn, Len(strRowColumn) - lngCount + 1)
End Function
Option Explicit
Public Type RowColumn 'function requires a user defined type
row As String
col As String
End Type
[/vba]
But this is for parsing a would be Access column Name (which represent it's intended location in Excel) from Access to Excel.
This is what I use when I need a column letter:
[VBA]
Private Sub Worksheet_SelectionChange(ByVal Target As Range)
GiveColLeter Target.Column
End Sub
Public Function GiveColLeter(iNumber As Long) As String
Dim A As String, B As String
If iNumber \ 26 > 0 Then A = Chr(64 + iNumber \ 26)
B = Chr(64 + ((iNumber / 26) - (iNumber \ 26)) * 26)
GiveColLeter = A & B
End Function
[/VBA]
a few more pennies on the stack :devil2:
This is fantastic! What a great variety of ways!
I have to say that I find it pretty funny on those occasions that I write 50 lines of painstaking code, only to have Bob come along and give a 50 character formula to do the same thing. :)
In the immortal words of Buzz Lightyear, "You're mocking me, aren't you?!"Quote:
Originally Posted by Ken Puls
:rofl:
Ken, I know what you mean.
:rofl: I've already added it to my list (got 7 short ones now)Quote:
Originally Posted by Ken Puls
I use something similar to Bob's, although it works with 97 as well...
[vba]Function ColLet(lngCol As Long) As String
'---------------------------------------------------------------------------------------
' Procedure : ColLet
' DateTime : 6/2006
' Author : Zack Barresse
' Purpose : Return a column letter from column index value. 97 Compliant
'---------------------------------------------------------------------------------------
Dim strAddy As String
ColLet = "ERROR!"
On Error GoTo 0
strAddy = Cells(1, lngCol).Address(False, False)
If Err <> 0 Or strAddy = "" Then Exit Function
ColLet = Left(strAddy, Len(strAddy) - 1)
End Function[/vba]
Of course, the downside, if there is not an activesheet, it fails.
So does mine!Quote:
Originally Posted by firefytr
Downside of using built-ins.Quote:
Originally Posted by firefytr
8...
[VBA]
Sub ColumnLetter3()
Dim Addy As String
Addy = ActiveCell.EntireColumn.Address(0, 0)
MsgBox Left(Addy, Int(Len(Addy) / 2))
End Sub
[/VBA]
The Split() function works in 97??Quote:
Originally Posted by xld
No....Quote:
Originally Posted by firefytr
...
I'm trying to understand how Bob's function works in 97, as I do not have it installed to test it. Bob, Ken, anyone mind filling in the gaps for me?
[vba]
#If VBA6 Then
#Else
'-----------------------------------------------------------------
Function Split(Text As String, _
Optional Delimiter As String = ",") As Variant
'-----------------------------------------------------------------
Dim i As Long
Dim sFormula As String
Dim aryEval
Dim aryValues
If Delimiter = vbNullChar Then
Delimiter = Chr(7)
Text = Replace(Text, vbNullChar, Delimiter)
End If
sFormula = "{""" & Application.Substitute(Text, Delimiter, """,""") & """}"
aryEval = Evaluate(sFormula)
ReDim aryValues(0 To UBound(aryEval) - 1)
For i = 0 To UBound(aryValues)
aryValues(i) = aryEval(i + 1)
Next
Split = aryValues
End Function
#End If
[/vba]
Bob,
Not to split hairs, but doesn't the conditional compilation mean that it is essentially ignored in 97? I'd hardly say that qualifies as "works".
Let me know if I'm missing something...
I see now. Yeah, technically it will work in 97 through the use of a UDF to simulate the use of the (post 97) native Split() function. I should have said my function will work - natively - from 97 and up. ;)
Ah! I focussed on the conditional compilation, and missed the fact that there was an entire function nested in there! :doh:Quote:
Originally Posted by Ken Puls
Very clever
No it means that it is not ignored in 97.Quote:
Originally Posted by Ken Puls
And it works. The VBA routine that I provided runs in any version of Excel, just so long as you also have the conditional code.
Now that really is splitting hairs. You add code beacuse some function is not built-in, and then complain because someone else adds more code because some function is not built-in to a particular version!Quote:
Originally Posted by firefytr
Callbacks don't work in 97, but it is possible to write code to emulate them, just as that code emulates Split.
I totally mis-read your reply. What prompted my answer was that I *saw* this:Quote:
Originally Posted by xld
[vba]
#If VBA6 Then
'-----------------------------------------------------------------
Function ColumnLetter(Col As Long)
'-----------------------------------------------------------------
Dim sColumn As String
On Error Resume Next
sColumn = Split(Columns(Col).Address(, False), ":")(1)
On Error Goto 0
ColumnLetter = sColumn
End Function
#Else
#End If[/vba]
... which is, of course, not at all what you actually posted. One look at the conditional blew me totally off course here. And for some reason, once that got into my head, I just couldn't see through what you actually wrote. Weird the way the brain can do that to you. :think: At any rate, very much my bad. :)
Having re-read (and understood) your answer, I agree that it does work. It's not native, (and doesn't need to be,) but I quite like it. :yes
I don't think it is really splitting hairs, I was only trying to point out an issue which I feel is quite valid. I know there is a workaround, but if I can make a call with one function rather than two, I'd rather do that. Personal preference only. :)Quote:
Originally Posted by xld
I see where you're going, but I remain steadfast that I was not complaining, merely pointing out an issue. You never mentioned that you needed to substitute a UDF for the later-native Split() function. So, as I assumed that others may assume (double-assumption??), I only mentioned the fact that my function would work (I should have added the keyword, "alone") in 97 and up.Quote:
Originally Posted by xld
I realised that when I saw your follow-up. I think we were composing them at the same time.Quote:
Originally Posted by Ken Puls
Tell me about it!Quote:
Originally Posted by Ken Puls
I have 97 versions of InstrRev and Join as well.Quote:
Originally Posted by Ken Puls
Split is a function call whether it is a built-in function or a hand-carfted function, it is still a function call. And the hand-crafted only comes into play in 97.Quote:
Originally Posted by firefytr
Nobody mentioned 97 when I posted it, so it is not surprising that I didn't mention it needed a custom function (not a UDF). Neither works alone, they need to invoke a Split function, which ... see above.Quote:
Originally Posted by firefytr
You're right, Split() is a function call. But it is not in every OM, whereas I believe Left() is. The point being, less work, more portability, less maintenance and less troubleshooting, all with the same results. It's splendid that one can create a UDF to emulate the native Split() function (and I happen to love the native function, great add) although I see no monetary gain, especially here. IMO, the function I have posted is superior due to these facts.
Well of course they all invoke calling other functions! Why would one need a UDF if they did not! :DQuote:
Originally Posted by xld
('97 compliant)
[vba]Function ColumnLetter(Col As Long) As String
ColumnLetter = Left(Columns(Col).Address(0, 0), Int(Len(Columns(Col).Address(0, 0)) / 2))
End Function[/vba]
Split is in my version of 97 just as much as it is not in yours. Would it be more acceptable to you if I stuffed it in a DLL and you didn't see my FUNCTION? After all, this is exactly what MS have done, their Split is buried somewhere in the code that Excel links to.Quote:
Originally Posted by firefytr
It is totally portable, because the function is in the workbook that uses it. I stick it in a separate 97 module, it has been debugged, I have been using it for many years and haven't touched it since it was written. It is portable, no maintenance, no troubleshooting.
What has monetary gain got to do with it?
I repeat, it is a function, not a UDF. Other than that, I don't understand that sentence at all.Quote:
Originally Posted by firefytr
While not intended as a question, there have been so many solutions, I've moved this to the Excel forum.
I think this will work as well.
Return Column Letter.
=SUBSTITUTE(ADDRESS(1,COLUMN(),4),"1","")
Return Cell Address
=ADDRESS(ROW(),COLUMN())
No, if I were using 97 and had a use for the Split() function I would be using that as well. But I'm not, so I won't. I don't try to compare to native functionality. Not really sure why you do either.Quote:
Originally Posted by xld
I understand it is portable, and that is handy I'm sure. It's still more work than you need to do, and I'm not into making more work for myself.Quote:
Originally Posted by xld
Maybe that wasn't the best way to describe it. Maybe I should have said "advantage". I see no advantage to using a UDF where built-in functionality is available.Quote:
Originally Posted by xld
Not a UDF? How do you figure that Bob? You lost me there..Quote:
Originally Posted by xld
I also had some interesting time trial tests using XL 2003. I also threw in Johnske's because, well, I like his function too.
Honestly, Zack, sometimes I think you argue for the heck of it... But if you want to argue... :dunno
I like Bob's approach, simply for the fact that it is forward compatible with native functions in later versions that I would use. By using the conditional, we gain the efficiency of the native version in later Office installs.
:)
That makes 10 I've got in my 'collection' now :rotlaugh: :thumbQuote:
Originally Posted by Shazam
LOL! Okay, I've made the points I've wanted to make, so I'm done. I'm not arguing to argue, I don't like Bob's solution very much and I would never use it. Conditional or not. That is only my opinion. :)
NEVER?
So, if you are coding to 97, and there is a need to get an array from a string, what would you do?
No Bob, you misunderstand. If I had a need for the Split() function in 97, I would think about the conditionally compiled UDF, of course. For something such as this [thread], no, I would never use it.
Can we do a conditional compilation to test for Excel 2007?
Think Application.Filesearch. Theoretically, we could create something similar for this function to avoid re-writing the function in the initial upgrade of a file. You bemoan the loss of Filesearch, would you use it for that?
No Ken, the VB version is still 6, you must only do a version check. Excel 97 was still based on VB5, hence the compilation check. And as sad as it is about FileSearch, I must abandon that as well. I prefer to use code that is compatible in many versions. I hate narrowing the margin.