>>>>>Split() expects array:
>>>>>

>>>>> string[] vs = SearchString.Split( new  Char[] {':'}  );
>>>>>

>>>>
>>>>Unfortunately, that didn't solve the problem...just re-arranged the order of the errors in the Output Window.
>>>
>>>Sounds we're back to days of Cobol (as your tagline reminds us), where getting a different error was progress.
>>
>>True, but COBOL would at least tell me a general area for the problem.
>
>Yup, it had some rules, because it was a simple single-pass compiler. Look at the first line with the error - everything beyond it is the stupid compiler trying to parse the rest as if the error never happened, and reporting dozens of phantom errors. As the old rule went - it says 200 errors, you fix two, you get 30; you fix three more, you get 7, you fix two more, you get 28.

True, true...I headdesk'd many a times on that very thing with both Cobol and FORTRAN (yeah, dinosaur here).

Oh, and one of my new faves for VS. Apparently I violate naming rules with things like rbAccess_Chkd as a method name.