Thanks, Vlad

I used that idea to make the simpler conversions like changing := to = and stuff like that. Maybe I could modify the converter to handle this too...

I'll look into it, thanks again

>Not very helpful, just a "generic" idea. If the old system is full of these arrays and if it seems that you'll need to rewrite all the code involving these arrays: try to see if you can come with a VFP solution that and write a code convertor for the old code to new code. It may be doable and it may require less time to develop. Another big advantage would be that if you want to change something in the VFP solution, you'll have to change only the convertor and not to go to make changes in all places where you modified before.
>
>Unfortunately, I don't know Clipper, so I can't help you with ideas for your specific problem.
>
>Vlad
>
>>I've been working on converting a system from Clipper to VFP. The Clipper version uses nested arrays _everywhere_ !!
>>
>>Since VFP does not support nested arrays, I need to use another sensible approach. I know that I can point a null array element to a seperate array object, but this does not support the way the arrays are used in the system.
>>
>>Here are some sample lines of Clipper code which I must convert. Parenthises are actually the curly brackets, but I can't post those in a message.
>>
>>

>>
>>DECLARE aArrayName = () <-VFP does not allow arrays with 0 elements
>>aArrayName = (element1, element2, (element3_1, element3_2)) <-sub-array
>>Aadd( aArrayName, (element1, element2, (element3_1, element3_2)) <-adding elements to an array (and the sub-array)
>>

>>
>>TIA
>>
>>Larry