> > Hi,
> >
> > There's a lot of alternative techniques in VFP. And that's what the so-called "flexibility". I also tried to used your given example.
> >
> >

lcAppend = [APPEND FROM (DBF("SourceTableAlias")) FOR RECNO(("SourceTableAlias") >= 1000]
> > &lcAppend
> > 

> > ... =)
> >
> > Christian M. Tabligan
> >
> > Visual FoxPro is like a game...need to explore until you reach your goal to success!!!
>
> Of course, colleague, if you need to build a command with unknown values - macro is the tool of choice. For instance, in a function/method manipulating a given table/alias, in order to leave the everything as it was in the beginning when exiting, I do
>
>

LPARAMETERS tcAlias
> LOCAL lcPrevArea, lcPrevRecNo
> 
> lcPrevArea = [SELECT ] + TRANSFORM(SELECT(ALIAS))
> lcPrevRecNo = [GO ] + TRANSFORM(RECNO(tcAlias)) + [ IN ] + tcAlias
> && Whatever the code needed to be executed; and on exiting
> &lcPrevRecNo
> &lcPrevArea
> RETURN luRet

> But then - again, I found out (after introducing Win9.xx and WinNT4, with the long folder names containing spaces, ampersands, etc.) that macro often got confused. I switched to implicit EVAL() (what in fact "()" is) - and it worked. I tried to use () wherever I could and it worked in most of the cases where I needed.
>
> Again, it's the matter of choice, mostly.
>
> Regards,
>
> Ilya

...hmmmm???? You really impressed me for introducing the advantage of "()" Ilya. I gave you a credit for that! =)


Christian M. Tabligan

Visual FoxPro is like a game...need to explore until you reach your goal to success!!!