In the example below what happens to the lock?
Does it release if the write is not executed?
If not shouldn't you have a RELEASE statement at the end after the last END?
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf
Hi Everyone,
Does a DCOUNT get evaluated again for each iteration of a loop?
Or is UniVerse these days intelligent enough to keep track of what's going on?
e.g.
for i = 1 to dcount(array,@fm)
*commands here
next i
versus
totalattributes = dcount(array,@fm)
for i = 1 to totalattributes
*c
The only way that this could not be an issue is if the compiler and the smarts
and determined ahead of time that the array was invariant.
My bet is solidly on plan b.
-Rick
On Feb 10, 2013, at 9:14 PM, Peter Cheney wrote:
> Hi Everyone,
>
> Does a DCOUNT get evaluated again for each iteration
If order isn't important
for dcount(array,@fm) to 1 step -1
*commands here
next i
Should only have the dcount evaluated once on any platform/release I believe
Ross Ferris
Stamina Software
Visage > Better by Design!
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto
