Recent content by AccessOfEvil

a rather long swim from there I'm afraid...I think it maybe should be "MinOfFile" rather than "MinOfFileName"?

From what I understand this looks reasonable. You could get into some more elaborate coding, but this should suffice. You might double check the logic of the criteria. You probably want to use Not ("A" or "H") instead of Not "A" or "H" or even try Nz([Expired],"") Not In ("A","H")...

Depending on your version of Access you might be able to put a calculated field in a table. However, the fact that users can change the field directly would mean you probably don't want to do that. You can use your logic of =IIf([ReviewDate]>Now(),"Y","N") within a query if you needed to...

Hmm...without really seeing the data, I'm just going to make progressively stupider guesses. :confused: One thing to verify is that none of the remaining duplicates share the same folder name. In other words, the original idea of "save the lowest/first folder of each set of duplicates on...

As far as the remaining 120 duplicates, it's hard to say without looking at the data (which I understand you can't share), but one guess is that you need one or two more fields to make the data truly unique. In other words, you thought that From, Subject, and Sent are enough to uniquely...

In your qryImportant Emails, you are renaming the columns (not sure how this happened), so that if you look at the results, "From", "Subject", and "Sent" have been replaced by "Expr1", "Expr2", and "Expr3". I think this is why the next query is complaining - it can't find "From" (or "Subject"...

Assume your table is tblEmail with these columns: ID, DataSet, Folder, From, To, Subject, Body To group the records by From/To/Subject, selecting only the lowest/first DataSet for that set of duplicates, you can create a query qryImportantEmails as follows: SELECT Min(tblEmails.Dataset) AS...

Well you sort of answered your own question...the underlying query is the problem. It is hard to say exactly what the problem is without knowing the overall structure of the database, but a good thing to keep in mind is that subform should really just represent a one-to-many relationship (with...

It seems to be sorting in alphabetical order (so 100000000000 would come before 2, just as A is before B) rather than numerical order. It looks like you have defined your datatype in the underlying table as Text rather than Number (maybe Text is the default so you just left it that way when you...

Hi, I'm an MS-Access developer in the Boston (US) area. I've been working with Access versions from 97 thru 2010 for the last ten years or so. I have kind of a love/hate relationship with it - it is great for RAD, but it is limited in so many ways. I have worked quite a bit with SQL Server...