If you can define exactly which fields you require I  will do you an XML report which will pick up just the latest record for a site.  If you have vague dates in your system then please can you also advise how you want the latest record identified (ie based on vague date start or vague date end). Also do ou have a Location hierarchy in place and if you do, then do you a want to include sub site data ?.

Linda

I have had a go at this and the zipped file is at

http://forums.nbn.org.uk/uploads.php?file=LC_LatestRecordForSite.zip

Unzip the file into the User File/Reports folder of Recorder 6 and you should see the report in Report/LCReports, or you can run it as a quick report by right clicking on the Locations and selecting the report from there.

I have added a second report which gives the same information but for all records for the location. This can be used to check the report and may be of general use. 

Both run, but I haven't done much testing on what happens in various situations.

Let me know how you get on.

I have been working on just such a report for polygons, although perhaps rather simpler in terms of output fields, Linda, when we have tested it a little more comprehensively I would be happy to pass it on.

Looking at your specification Linda I forsee a little difficulty. I have been working on this query in order to generate site species lists (rather than a list of records) which summarise both records associated explicitly with the site and those which have spatial refs falling (partially or wholly) within the site boundary but which are not specifically recorded as at the site. In order to make this work and correctly return only one date per taxon (in my case the vague end date rather than start, but no matter) it has been necessary to include (apart from the date) only fields which relate to the taxon (latin name, common name, status etc), rather than those which relate to the occurrence (e.g. location information, determiner etc).
This is because the query must group the occurences by all the non-date fields in order to function correctly. The problem then is that if you include all the other fields you will end up with a list of records, rather than a list of species.
It would be possible to add all the other stuff back in after the main part of the query has run, but the means by which this was done would need careful consideration.
For example if the polygon contains several records for a given species, these will most likely all have different recorders and determiners, perhaps different NGRs, locations, comments. Would you want to only return determiner etc. for the most recent record of a given taxon?

I think I should go and look at what Mike has already given you...

Thanks both; sorry not to reply sooner, I've been away for a while.
I'll see what I can do with Mike's query, and try to work out a way of using it for polygons.  It should be OK, although I might simplify the fields chosen.