Hi Larry,

You are quite right in your point - it is only a one dimension array. But the weird comes in here. Primary I have found a workaround - (and got some more from you fellows!). But the problem is the same when you (on my machine!) is trying to make a property array like myarray(1,2) - you have to write myarray(1.2) (dot), and the property text writes myarray[1,2] (comma). If you write myarray(1,2) (comma) it responds "invalid name".

So your point is right. My point is, there is a "bug" in some way - like Michelle proposes - it has probably something to do with in our region we write one million like 1.000.000,00 - you do it opposite. I have tried to change in VFP and WINDOWS, but it did not immediately give a solution.

Thanks for your interest

Lasse

>No it's not. As I said in my previous post it is not really a two-dimensional array. VFP displays ?,0 for 1-dimensional arrays in the property sheet only. If you perform an ALEN() on it using 2 as the second parameter to retrieve the columns, you get 0 (no columns).
>
>As others have said, if you want to create an array property set the name to myArray[1]. This creates a 1-dimensional array property. If you need to change the dimensions, change it in code at the appropriate time. You can dimension it to two dimensions at that time (if needed).
>
>>Hi Larry,
>>
>>I got your point, but here the funny things comes in. In the resulting name of the array (property window) i says myarray[1,0] if I enter myarray(1.0), so it acceps it as a 2 dimensionary array! ?????
>>
>>Perhaps it has something to do with my different way og notating values here in Denmark??
>>
>>Thanks
>>
>>Lasse
>>

>>>>I have tried several words - it's the same. But as I've mentioned - in a later mail..., myarray(1.0) works, but myarray(1,0) doesn't only dot as difference, comma doesn't work. I do not understand that.
>>>>
>>>>Lasse
>>>>