The grid squares are all stored in a table called GRID_SQUARE (unsurprisingly).  It looks to me like you should be OK to filter this appropriately and delete as many of the records (for which you are custodian) as you wish.

I can't promise that. The obvious problem is that the validation routines which test new records to see if they are within a location will not work so you may not be able to enter any data for the locations.

What is the problem with having grid squares populated? Why do you want to delete them?

I must admit that I have thought about doing this but never tried it. Many of our locations which came originally for Recorder 3 have a 10km grid square associated, which means that the validation is pretty poor, since any record within that square can be attached to the site. If I had the time I might try deleting the lot and recreating using the tool in Recorder

Grid Squares are optional. So there is no problem deleting them.  Their main use is to provide validation for data entered against a location. Any data entered against a location is checked to make sure it falls within the grid square of the Location. If there are no grid squares for Location then the entry is accepted. As Rob says there is only one table involved GRID_SQUARE.  A batch update would do the job. The query for deleting all of them in your system would be DELETE from Grid_Square where Custodian = 'your site id', but you may wish to apply other criteria.  You shouldn't  delete the grid squares for locations where you are not the Custodian as potentially this cause problems if the data if  passed to others.
     

Mike

Mike