This is a classic case of a situation where one should do what works and not
worry about why something else doesn't.
set relation to nJobID into crap
delete for !EMPTY(crap.nJobId)
works.
That's the major advantage we have with Foxpro; there is always more than one
solution to any programming problem! We're so lucky compared to those poor sods
who have to use VB or Access...
Chet
----- Original Message -----
From: "Michael J. Babcock" <vfpmcp /AT/ mbsoftwaresolutions D.OT com>
To: <profoxtech@leafe.com>
Sent: Saturday, February 28, 2004 8:53 AM
Subject: Re: DELETE FROM with subselect
> Brian Abbott wrote:
>
> > Does this work?
> >
> > USE jobs
> > DELETE FROM jobs WHERE nJobID in (select njobid FROM crap)
>
> Nope! http://mbsoftwaresolutions.com/images/nope.JPG
>
>
> --
>
> Michael J. Babcock, MCP
> President/CSA, MB Software Solutions, LLC
> http://mbsoftwaresolutions.com
> "Bettering your bottom line by helping you work smarter, not harder,
> with custom software solutions."
>
>
[excessive quoting removed by server]
©2004 Chet Gardiner |
