Adherence to the Option Base 1 setting?

[GraeagleBill]

Any way to force the Split function to adhere to the Option Base 1 setting? Works okay for static declarations but ignored with dynamic allocations. Maybe a hidden option in the parameter list to Split I missed?

Option Compare Database
Option Explicit
Option Base 1            <<<<<<<<<<<<<<


Const str As String = "Marge, Mary, Joan, Jason, Michael & Peter - Plus Henry, Philip, & Macy Head - & Joseph Arnold"
Dim strChList As String
Dim strTst As String
Dim Ndx As Integer
Dim MaxNdx As Integer
Dim ChAr() As String          <<<<<<<<<<<<<<
Dim LnAr(10) As String       <<<<<<<<<<<<<<
Dim lngMaxLn As Long
Dim Lndx As Integer
Dim ISayStop As Boolean
Dim DoLine As Boolean
Dim I As Integer
Private Sub tst()
lngMaxLn = 2160       '1.5 inches
lngMaxLn = 2880       '2.0 inches
lngMaxLn = 2760       'TMS profiles
strChList = "Marge, Mary, Joan, Carol, Jason, Michael & Peter - Plus Henry, Bill, Lori, Philip, & Macy Head - Plus Joseph & Kathy  Arnold"
Lndx = -1
strTst = ""
Ndx = 0
ChAr = Split(strChList, " ")
MsgBox "lbound(ChAr) = " & LBound(ChAr) & "  lbound(LnAr) = " & LBound(LnAr)

[Micron]

A lot simpler to Dim the array to start at one?
ChAr(1 To 10) As String

You're liable to confuse anyone by using Base 1 - including yourself later on.

[GraeagleBill]

Yes, the use of Base 1 can cause more confusion than one desires. I don't think I've used it in well over 10 or 12 years, and even then is was a strange situation to begin with. The issue with the OP is that "Split" doesn't adhere to the module's Base setting, thereby creating a major inconsistency nobody wants to deal with. I'll leave the OP unsolved for now and return to Base 0 as I've always done.

Four inches of new snow in Reno this morning that we don't need, maybe we can ship it up to you up there if you run short

[Micron]

Bring it on! I have an Outback that I personally know will plow through 17" of new snow as if it were nothing.
Split returns a zero based array, or so says the documentation so I'd say you're stuck with it.

You declare a const and a string for the same thing? By splitting at space you want list values like
Michael
Peter
&
-
Plus
Henry
and so on?

[GraeagleBill]

That's just a test string you can ignore. I just wanted sample code that demonstrated the lack of consistency with the BASE between static and dynamic dimensions.

Ah yes, when we still lived in Graeagle, plowing 18" of new snow off the driveway was always fun. Reno by comparison is "child's play"

[Micron]

lack of consistency with the BASE between static and dynamic dimensions

Say whaaat?
If a tool makes one thing and you use that tool, don't expect it to make something else.
I suppose you could first make a post, then a toothpick:

ChAr = Split("Marge, Mary, Joan, Carol, Jason, Michael & Peter - Plus Henry, Bill, Lori, Philip, & Macy Head - Plus Joseph & Kathy  Arnold", ",")
For I = 1 To UBound(ChAr)
     ReDim Preserve ary(I)
     ary(I) = ChAr(I - 1)
Next

Lndx = -1
strTst = ""
Ndx = 0

MsgBox LBound(ary)
MsgBox "lbound(ChAr) = " & LBound(ChAr) & "  lbound(LnAr) = " & LBound(LnAr)

So ChAr becomes ary, which is one based.

You realize that ChAr is Char, a reserved word?

[GraeagleBill]

I'd start laughing, but with the headaches I've experienced with the changes to this historic app, it's not funny. "ChAr" as typed with capitals obscured that I was messing with what I already know is the reserved word "Char". I believe the original intent was to be short for "Child Array". Conventionally, it should have been "strChAr" to begin with. I think I'd better do a thorough audit of this old app to see where else there might be a snake hiding in the grass.

Thanks for the wakeup call..............

[Micron]

Except for the obvious and oft used things like sql, i, x, n, etc. I usually 'type' my variables, so yeah, strChar for sure.