Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. mickeyziggyk

    Temporal query (all rows starting at the closest date to Jan 1st 08)

    Thank you all for your time and suggestions. I came up with a slightly different solution as there are more conditions than I mentioned (thanks PH as otherwise your solution is very concise) What I appreciated most was the manner in which you approached the problem and broke it down into...
  2. mickeyziggyk

    Temporal query (all rows starting at the closest date to Jan 1st 08)

    Hello All I work with a HR db that has no end dates built into its design. I only have effective dates that represent the start of a change to an employee's profile. I want to see all records/changes about every employee from the date Jan 1st 2008. But some employees have had no changes to...
  3. mickeyziggyk

    Aggregate SQL queries in Access / duplicates that are NOT max

    FYI Leslie I had some trouble with your suggestion so after a little tweaking (and it is great to know that you can nest after the join statement) and I got the code below to delete those tuples / rows that were duplicates and not the maximum emp_rec_no: DELETE * FROM Tablename WHERE id1 in (...
  4. mickeyziggyk

    Aggregate SQL queries in Access / duplicates that are NOT max

    Leslie It makes perfect sense, thank you very much (I did not know you could nest after the join statement, I will start experimenting!) Michal
  5. mickeyziggyk

    Aggregate SQL queries in Access / duplicates that are NOT max

    Greetings I think I have an interesting question that has me baffled. It is as so: I have a relation/table that has the following structure: ID1 (auto int pkey) ID (text / char) Empl_recd_no (int) There are duplicate entries within the attribute / column 'ID'. For each duplicate entry there...

Part and Inventory Search

Back
Top