🚀 go-pugleaf

In article <36CE28AB.704C343B@nospam.mcbsys.com>, Mark Berry politely 
paraphrased ...
> After reading the posts here under the "Query troubles" topic, I'm
> wondering whether this whole thing may have to be re-written
> anyway--will I be able to delete the orphaned records if I ever get this
> JOIN to behave?
> 
If the result is readonly you won't be able to delete them, behaveing or 
not. I'm by no stretch of imagination an SQL guy, but this works for me, 
try it out.

close all
erase master.dbf
erase child.dbf
if not file("MASTER.DBF")
  create table "master.dbf" (order_id char(2))
  use "master.dbf"
  generate 10   //10 records from 01-10
  replace all order_id with str(recno(),2,0,"0")
  use
endif
if not file("CHILD.DBF")
  create table "child.dbf" (order_id char(2))
  use "child.dbf"
  generate 7   //7 record from 01-07
  replace all order_id with str(recno(),2,0,"0")
  use
endif

DELETE FROM MASTER M WHERE NOT M.ORDER_ID IN;
      (SELECT ORDER_ID FROM CHILD C WHERE c.ORDER_ID=M.ORDER_ID)
use master
//now 08.09 and 10 which where not in child.dbf
// are also deleted in the master
browse 

-- 
Romain Strieff [TeamB]
Please read this newsgroup guide below before 
posting on the private Inprise newsgroups.
http://www.inprise.com/newsgroups/guide.html
--