I still have to use (but not for much longer
) VPME and xCase2VPM and I will not miss either. I will certainly not miss the quirks or the extremely tedious view generation process that takes forever to run for a simple change
Or the massive list of views which contain many more fields than I actually want to query or the generation of "SELECT *" type statements which causes VFP to throw an error when the field order changes.....
To be honest, I was worried initially about SF as you code your own queries and I assumed this would be hard work. However, after using SF, it is a MUCH better approach and is extremely easy to do. Now the SF version of my VPME application is only quering the fields I need rather than some expanded list of fields created in a view generator.
I have been using SF every day now for months and I haven't found anything yet to grumble about I am really angry with myself for not finding it years ago but I am determined to find something wrong with it so I can grumble However, I suspect it will be a spelling mistake somewhere rather than a design flaw.
The best advice I can give anyone coming from a VPME background to SF is to totally forget about VPME and views. SF is in a different league and comparisions are pointless.
Just my 18 cents worth (sorry inflation).