RE: SQL Deletes

Honestly I would journal the files and commit after processing all 7
files.  Roll back on you Fail.  A little system administration and real
easy application programming that would be easy to follow for the
programmer behind you. 


Chris Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jen Raihala
Sent: Tuesday, September 13, 2005 8:08 AM
To: midrange-l@xxxxxxxxxxxx
Subject: SQL Deletes

Good morning from a slightly damp Midwest!

I have a question regarding multiple deletes in a RPG
/Free program I am writing. I have a status field
that, at anytime during the parsing of an XML "sheet",
can be set to 'F' to fail a document (through errors
like letters where there are supposed to be numbers or
blanks for required information). 

The program ultimately updates/writes to 7 different
db files, BUT it writes as it goes (I chose to reuse
certain fields rather than trying to guess how many
unique fields I would need since using arrays was
poo-pooed by the team leads). So if file 4 fails, then
there are fragments in 1,2 and 3 that I need to get
rid of. I think an SQL delete would be faster to write
than a set of repeated CHAIN deletes. 

How would I pass in the parameters of document number,
date and year? I honestly havent messed much with SQL
since school (and that was only on a faked up Oracle
db for Oracle class).