On Wed, 03 Dec 2003 20:07:58 GMT in comp.databases.ms-access,
dXXXfenton@bway.net.invalid (David W. Fenton) wrote:
[color=blue]
>tom7744@no.spam.cox.net (Tom van Stiphout) wrote in
><e7srsvgqgomut9hqntbbld5d28j26018q2@4ax.com>:
>[color=green]
>>On 3 Dec 2003 13:51:56 GMT, Keith Wilby
>><keith.wilby@AwayWithYerCrap.com> wrote:
>>
>>MoveFirst is not needed. A new recordset is either at EOF if no
>>rows, or at the first record.
>>But the fellow needs MoveNext, as well as the Loop instruction at
>>the bottom of the loop. The code as presented will not compile.[/color]
>
>MoveFirst may be unnecessary, but I always explicitly include it,
>anyway, just so it's clear where we're starting from.[/color]
I had a situation recently where the client has requested something
unatrual for a database to do, in an MTO or requisition they want a
start and end item number so they enter start item 1, end item 20, qty
20. This will later be split down upon reciept and the individual item
given a UID, the last part being nothing I've not done before of
course it's the first part is peculiar to the way they work.
No if they enter item 1 to 20, you can't have say item 11 elsewhere,
etc, in the beforeupdate I created a recordsetclone and looped
through, I always had put .MoveFirst in the past but this time I
didn't (laziness I guess) and it would never trap the first attempt
after opening the form, upon debugging I found it looped just one
record so it had started at the last record.
I'll not be making that mistake again.
--
A)bort, R)etry, I)nfluence with large hammer.