>>Isn't it too much code for Inlist. IMHO System.Array class has corresponding (and much better) ways to implement it (like Exists, Find ...).
>
>I don't know. I need to simulate the VFP function as is. In VFP, I can make a call to Inlist() like that. So, I need to support the same in VB.NET. Some conversions I am doing contains a lot of Inlist() so we simply bind it with oApp.Inlist(). I just don't know why the parameters starting over 10 are ignored. It is as if it would be empty.

I mean rewrite your oApp's inlist so it accepts arbitrary number of parameters and returns result for any type. Here is declaration and usage of generic list class:

Visual Basic (Declaration) 
Public Function Contains ( _
	item As T _
) As Boolean
 
Visual Basic (Usage) 
Dim instance As List(Of T)
Dim item As T
Dim returnValue As Boolean

returnValue = instance.Contains(item)

Array and List generic classes support a number of methods to make it all easy.
IOW once you write your new "Inlist" you could pass more or less than 26 parameters and they might be string, int, a complex type etc.
I'd write code but you're using VB and I'm using C#:(
Cetin