Paradox Community

Items in pnews.paradox-dos

Subject:Re: One detail too hard
Date:Mon, 6 Aug 2018 12:17:24 +1000
From:Bernie van't Hof <berniev@bje.com.au>
Newsgroups:pnews.paradox-dos
Fixed. Thank you. Serves me right for being lazy.

On 5/8/18 9:55 pm, Steven Green wrote:
> just an FYI.. in the app I'm working on right now, there are several instances of the "fail"
line.. it works in 
> p9/10/11.. I'd have to look, to find examples in pdoxdos, but I'll take your word for it
> 
> 
> -- 
> 
> Steven Green
> Myrtle Beach, South Carolina, USA
> 
> http://www.OasisTradingPost.com
> 
> Collectibles and Memorabilia
> Vintage Lego Sets and Parts
> - and Paradox support, too
> "Bernie van't Hof"  wrote in message news:5b6314dd$1@pnews.thedbcommunity.com...
> 
> Cleaning up variable scoping and found an issue, but I'm not sure its worth worrying about..
> 
> Query
> 
>    Ordindhx | Date      |
>             | ~CurrDate |
> 
> Endquery
> CHECK
> [Ordinddx(Q)->DD#] = "_d,~CurrDD"  ; <<=== fails
> [Ordindhx(Q)->CN#] = CurrCN
> Do_It!
> 
> 
> If CurrDD is defined outside current function scope it will fail.
> 
> Workaround is to use = "_d," + CurrDD.
> 
> Is this worth chasing?
> 
> - Bernie


Copyright © 2004 thedbcommunity.com