(This mail was originally part of “FMP8 Max(Table Self:atum)+1”)

A number of records is added within a loop, the records have sequential
dates.

GetAsDate(Max(Table Self:atum)+1) is auto-entered data.
records are committed within the loop, after every “new record”.

When used with IWP, the trick doesn't work; max() never finds new dates
added with this loop. All new dates have the same value.


The internal relation (self) was based on a computation with global storage

When instead a computational field is used without the global storage
option, the records will be found with max(self:: etc) in next iterations.

When running in native mode, I don't see this differend behaviour.

Is this a FM bug or a FM feature?

In article <11mklkcm5jhj077 (AT) corp (DOT) supernews.com>, gertkok (AT) keraweb (DOT) nl
says...
I'd report it to FM as an IWP bug. I can't think of a legitimate
justification for it to work differently in IWP.

That said, there are better ways of accomplishing what you are doing.
Why not simply compute the first date, and (in pseudocode)

$date = startdate
$loopcounter = 0
$loopmax = x
loop
new record
set date startdate + loopcounter
loopcounter + 1
exit loop if $loopcounter = $loopmax
end loop

What is the result when 2 or more users at the same time happen to
trigger the adding of 28 records?

I've been looking for a conversion integer-> date, but couldn't find it.


42 wrote: