Dump the records into a temp table.
Make sure you don't design a system that ends up loosing Data Entry somehow.
You could store info into an array, but what happens when a connection is
broken,etc... ???
""Asendorf, John"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I'm about to create a piece of a project which which will be used to check
> for errors in data entry. Every 500 records entered will prompt the user
to
> check their work. I have all of the triggers set up already. The
database
> is all Oracle, PHP 4.0.4 (1381 build). What I would like to do is display
> all of the 500 records (no problem) and (here's where I could use some
> advice) highlight any records with a duplicate value in one particular
> field.
>
> Should I load all of the data into an array? Should I skim through all
the
> records, take notes, reset, and then run through them again? Should I run
a
> separate statement which searches for dupes and then match them against
the
> whole body of records?
>
> I don't want code, just a voice of experience which could start me off
> right.
>
> Thanks,
>
> John
>
> ---------------------
> John Asendorf - [EMAIL PROTECTED]
> Web Applications Developer
> http://www.lcounty.com - NEW FEATURES ADDED DAILY!
> Licking County, Ohio, USA
> 740-349-3631
> Aliquando et insanire iucundum est
>
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
