I saw the wish List in UT, but it is seems to me that is really icomplete or we think that fox is complete. Here is a basic Wish List for me:
1.Language enhancements
1.1 Its ashamed that from the very good set of vfp string function the split function is missing. I am aware that you can build it via strtran and alines but this is not always a viable solution
2. DML.
2.1 The most of the table commands have now the "in" clause. Still there are some commands that you have to select the table first (I think you cant say ``pack in table '' command . It would be nice to have it there also.
2.2 Its really surprising for a Database centric language like fox, to be sometimes so hard to import a plain SDF file. For instance I always feel the missing of a command that given an ascii and a table to be able to say something like the following :
append from ascii_name in table_name field1 c1-5, field2 c15-25, … , fieldn c1-c14 for c1-15 = value
2.3 We all know that the vfp SQL doesn’t have all the ansi functionality. We can not have for instance subquery in the insert statement. Neither the lost ansi functionality can be duplicated via other commands as for instance the append from. Put as much as ansi functionality you can in the language
3. Object Orientation
3.1. Object persistence. Some say that persistence thru XML is possible. Save the object as XML then save it in a memo and restore whenever you want..
4. User Interface.
4.1 We all know the weaknesses of the VFP GUI. And don’t say that this is because we don’t want to sacrifice extended control properties and events. I don’t believe this. Even VB has now both windowless and window controls. I think we also deserve it …

5. Client Server
5.1. Unfortunetely VFP is not the right tool for client derver development at least comparing it with tools built for this functionality in mind like Powerbuilder.We want to use VFP as a client server tool. In reality we want to sell our applications to small to medium clients, which run them on a standalone pcs or on a small to medium sized LAN, but at the same time very easily to scale it to thousands of users by simply changing the back end keeping the fat client. This is irrelevant to the position of the vfp in the middle tier. I would like to see the Powerbuilder Data window functionnality into VFP. Some frameworks using both views and SQLPASSTHRU are not very successful because VFP is missing the client server functionality as other tools have (powebuilder) If MS thinks SPT is dead then she must do something to extend the notion of the view and make able to link the view (optionally) to an ado result set. Then easily we could drop the view on a form to make it bounded with the ado result set ...
5.2 In connection with the 5.1 ability to bind the activex controls with VFP views linked with ADO resultsets.
6. Menus
No I don’t need OO menus
7. Reports
Maybe I need OO reports …
8. Com Servers
Ability to the VFP servers to “publish” their events … But I think this will be done because of the positioning of VFP in the middle tier …
9.Debugger
We have already seen some improovements coming. But I did not see the most usefull, the ability to edit the code and the values of the variables while in the debugging window.
These for now …