Hi Christof,

Most items in your list is unimportant except SET SKIP TO. I assume many people, including some of my friends, are using it in coding.

If you try to rewrite the following code (just an example) in either SQL or VFP commands without SET SKIP, you will need much more lines.

Create Table Actors (Class v(1), Name v(30))
Insert Into Actors Values ('1', 'Peter')
Insert Into Actors Values ('2', 'John')
Insert Into Actors Values ('2', 'Mary')
Insert Into Actors Values ('2', 'Chist')
Insert Into Actors Values ('3', 'Benny')
Insert Into Actors Values ('3', 'Paul')
Index On Class Tag Class

Use Actors Again In 0 Alias Class1 Order Class
Use Actors Again In 0 Alias Class2 Order Class
Use Actors Again In 0 Alias Class3 Order Class
Set Relation To '1' Into Class1, '2' Into Class2, '3' Into Class3
Set Skip To Class1, Class2, Class3
Browse Fields Class1=Class1.Name, Class2=Class2.Name, Class3=Class3.Name For Recno()=1

Ben



>No, I don't try to. <s> The reason is that VFP has so much functions that only few developers actually still use such as:
>
>- offline views
>- SET SKIP TO
>- support for Macintosh code pages
>- DBCS support for asian character
>- right to left support
>- country specific collate sequences like CZECH
>- database events
>- @...GET
>- ColorSource property
>- Read compatibility mode for form sets
>- Control class
>- Control arrays
>- minus operator for strings
>- comma and semicolon operator in reports
>- COPY TO TYPE SYLK
>- general fields
>- ACCEPT
>- BROWSE PREFERENCE
>- SET MACKEY
>- _PLINENO
>- _VFP.Eval
>
>I could go on, but I think you get the idea. 95% of all capabilities is an awful lot more than supporting 95% of all commands, functions and classes to some degree. My current focus is on implementing everything you need to write mobile applications with features being implemented in order of demand.