What does VFP do when it "falls over?" Mine usually stays upright, even whilst complaining.
I'd suspect when you macro-expand tlist and it is an empty string, you're left with INLIST(nTa, ) which is a syntax error. instead, just before the CASE statement, make tlist = "Nonsense" + IIF(NOT(EMPTY(tlist)), ", " + tlist, SPACE(0)) That way, there is at least one non-empty element in tlist and it doesn't end with a comma when you macro expand it. On Wed, May 20, 2015 at 5:31 AM, Allen <[email protected]> wrote: > Hi foxgang > I'm not sure if I am lacking coffee this morning but I am having a brain > block with an inlist. > > nTa = 0 > tlist = "" > > I am doing a case and one of them is, > > Case nTa > 0 and !empty(tlist) and inlist(nTa,&tlist) > > I thought VFP went left to right with AND's. So I expected the case to fall > over with nTa > 0 and continue. And even then the !empty(tlist) should have > got it but it falls over with the inlist. I had to do it this way because > tlist comes from a form/class property. I could cheat and male tlist "none" > as nTa will always be numeric. > Just wondered why. I assume it's the compiler chugging. And if there is a > way. > Al > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4uz8p7ayvzqskfi0dhtzuk2gonktll7egx3kj5uh63...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
