>>>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 ?

No problem for WinDev. When I start typing the common name (of the table and a variable, for example) each is shown in the IntelliSense popup unless and untill the one or the other doesn't apply to the function or command I am using. iow, if I am using HSeek() to position a table then a variable of the same name will not be offered since it does not apply to the function. So the editor is taking care of such things.

Plus, the requirement by WinDev for you to define your variable's type before use immediately allows WinDev to know how to handle that variable in the IntelliSense and thus help your coding work. Same applies to the use of the Analysis. Initially I just didn't get that but now I can see that by using the Analysis (which is optional) you are telling WinDev something about your database (whether HyperFile or SQL or xBase or whatever database). And it can use that information to help you code quicker and more correctly catching or preventing many runtime issues before you run.


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

In VFP I used Scatter to and Gather from to copy a record to memory and back again. In WinDev I accomplish this with HCopyRecord(). See also here for a complete list of function related to HyperFile SQL Management:

http://doc.windev.com/en-US/?3044156

There are very many higher level constructs, far more than in VFP. PC Soft seem to add hundreds of functions in each release (yearly) which just aid doing stuff that you would need to code yourself.


>Anything similar to table buffering ?

Not sure if this is exactly the same but WinDev uses a 2-step approach to editing fields of a record. The fields are edited in what I call memory buffers and then you have to specifically tell it to modify the current record with those changes or to create a new record with those changes - HModify() and HAdd() respectively.

Opening files can also be done with various levels of access and file/record locking options.


> Replication

Built into HyperFile SQL


> SQL level on tables / cursors ?

You can dynamically, in-code define a table and populate it, index it, access it like a disk table. Optionally save it or close it/delete it. The built-in, royalty free database (in direct access mode and Client-Server mode) and this ability to deinfe table on the fly were big things for me. I use that a lot in VFP.


>Something to abstract data backend access like cursoradapter ?

I never used CursorAdaptor in VFP so cannot comment. However, you can SQL SELECT a data set from a table(s) and it gives you a result set that can be processed like a table, create a Query from it, create a View, edit it, populate a grid, etc.