>>I'd like to know two things: what does the code look like, and what is there that isn't working, in terms of porting an app from fox to windev - macros, name expressions, LLFF...?
>
>Code sample.

Coding into files follows more the convention of coding to object properties, so no special replace syntax.
Has benefits if you change your approach to object based by minimizng changes needed.
What happens if you have a table named the same way as a obkect vaiable in scope ?
Or will that throw an error on attempting as name conflict ?

And are there "higher level" language constructs like scatter to / gather from name ?

Anything similar to table buffering ? Replication ? SQL level on tables / cursors ?
Something to abstract data backend access like cursoradapter ?
(Just voicing my area of interest - I know that covers a lot and I should read up a bit myself -
but for me that is the fox sweet spot making it markedly different from other dynamic languages)

thx for the running reports

thomas