Re: Simple Select Query
- From: THINKINGWAY <THINKINGWAY@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 21 Dec 2007 12:48:00 -0800
It is a part of a larger strategy of importing data from spread*** that is
the only source for the data (read produced by another business entity using
another enterprise database solution). Additionally, I am exceedingly (or
excruciatingly) new at this and you may feel free (I would say in my case
obligated) to point out any inefficiencies with associated recommendations.
Prefer not to recieve criticisms without alternatives/suggestions though
because they're like driving down a dead end alley at 90mph (read, doesn't
ever result in anything good).
Thank you,
"Jeff Boyce" wrote:
Is this a one-time cleanup effort, or part of a larger strategy of putting.
records in one table, then moving/copying them into another table? If the
latter, that's a very spreadsheetly way of approaching this. (hint: that's
not considered a compliment in these newsgroups...<g>)
Regards
Jeff Boyce
Microsoft Office/Access MVP
"THINKINGWAY" <THINKINGWAY@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0DFEA625-23DE-4BD5-952C-2226969B9F18@xxxxxxxxxxxxxxxx
I am trying to perform a select query to select all records that are NOT in
both tables. So I have tblPROJHIST and tblWMSNEW and they both have
project
# fields. What I am trying to do is find all the new project # records
in
tblWMSNEW that are not in tblPROJHIST and put them in tblPROJHIST.
Thanks
- Follow-Ups:
- Re: Simple Select Query
- From: Jeff Boyce
- Re: Simple Select Query
- References:
- Re: Simple Select Query
- From: Jeff Boyce
- Re: Simple Select Query
- Prev by Date: RE: Access Append Query to update Sequence Generator in Oracle
- Next by Date: even or odd records
- Previous by thread: Re: Simple Select Query
- Next by thread: Re: Simple Select Query
- Index(es):