It is possible that you will import records which fail R6 validation. All records are imported and there is no validation.  If the date records allowed from is set to a past date and there is no end date than this isn't going to be  a problem. If you have set a bounding box then you could potentially import records which will fail validation, becaus they are outside the box.  The approach I use with ER is to get the records into R6 and worry about checking and validation in Recorder 6. All the records import  as unchecked so that I can looka at each one.  I also drag the Survey onto the map with the OS tiles loaded so that I can do a quick check that they look in the right place.  As far as validation against the Survey is concerned if you  right click on the Survey you can run revalidate records and this will show if you have anything outside the date range or bounding box.  If you do this after every import then this will be an effective way of  validating your data.

You are Ok having two apps. as long as you don't use them both on the same day. If you need to do this then the Batch Update needs a slight change.

I had already done this for my own use  and have made this  available at

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

This includes a version of the Batch Update and the Report which have the option to select the EasyRecorder app which originated the data.  A code from this is then incorporated into the key which goes into the sample reference, allowing data from multiple apps to be processed in a day.

Mike Weideli
JNCC Approved R6 Expert