I don't think it's a bug because in m.X.Top FoxPro expects m.X to be an object and it isn't an object but array.

>Hi,
>
>

>DIMENSION X[1]
>x=3
>? x
>*X=_SCREEN   &&  this is a trapped error
>			&& ( populate a array with a object ref is ugly )
>X[1]=_SCREEN
>*** BUT read first element of array it would have to work
>? m.X.Top	 && <---- it is documented this behaviour limit ?( for me it is a bug )
>? m.X[1].Top
>

>
>The workaround is simple,
>but if i use a procedure with a parameter for simple scalar object or complex array structure,
>is need complicate the parameters or the code :
>

>PROCEDURE pippo(vaParameters)
>* vaParameters is a for reference parameter
>* vaParameters can be a scalar or a array
>* vaParameters first element is a object
>  IF m.vaParameters.something && i cannot do this directly
>    ....
>  ENDIF
>ENDPROC
>

>
>
>Fabio