It depends how many you have and how easy they are to identify.  Once the Surveys are deleted there is the option to delete them via the Data entry/Names and Addresses. If there are any records which use   the individual they will not delete. Otherwise a report or SQL on any individual with no data would a  possibility, or a Batch update which deletes individuals without any entries. Care needs to be used with the Batch Update approach, especially if the system has Tenure entries, or there are individuals who input data, but do not have any records.   If you let me know the situation on your system, I will advise futher or provide the reports/updates if required.

OK tried the update and it failed with a syntax error whilst running script 97 (usually this is something to do with our still being on SQL2000). The upgrade apparently stopped after the error message, eventually had to crash out of the updater. Recorder opens normally & reports version 6.21.1.270.

I tried to run the script (97) in Management Studio as this has usually enabled me to track down the syntax error, but in this case it has proved beyond my experience. Quite a lot of the script went through OK, but there were several messages as follows:

Msg 170, Level 15, State 1, Line 10
Line 10: Incorrect syntax near '('.
Msg 4902, Level 16, State 1, Line 2
Cannot alter table 'dbo.External_GUI_Link' because this table does not exist in database 'NBNData'.
Msg 208, Level 16, State 11, Line 3
Invalid object name 'External_GUI_Link'.
Msg 208, Level 16, State 11, Line 4

& Several duplicates of the last message (clearly the CREATE TABLE failed)

Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK_IW_Table_Rule_Post_Processing_Procedure'. Cannot insert duplicate key in object 'IW_Post_Processing_Procedure'.
The statement has been terminated.

I think recorder still works, but would really like to get to the bottom of this ASAP. Help

Rob

I think this is to do with using SQL 2000. Remove the whole contents of 0000097, just leaving a blank  file  and run again. It might stop on 9B. If so let me know.

Just to explain 0000097 was for version 6.20 and is completely replaced in 6.21 with 000009B. As most uses have not separately implemented 6.20 , script 0000097 is redundant.

Mike

After the previous failure, Recorder crashed on opening the Taxon dictionary, because of Invalid column name 'Preferred_Name_Attribute'.

This no longer happens, but the taxon dictionary window is empty

Much the same situation as before, seems to be setting the constraints on the primary key of a table?

Msg 170, Level 15, State 1, Line 10
Line 10: Incorrect syntax near '('.
Msg 4902, Level 16, State 1, Line 2
Cannot alter table 'dbo.Taxon_Occurrence_Ext_Ref' because this table does not exist in database 'NBNData'.
Msg 208, Level 16, State 11, Line 3
Invalid object name 'Taxon_Occurrence_Ext_Ref'.

That ran without incident thanks Mike.

However when I opened Recorder our Taxon dictionary browser window is still empty.

I exited and ran the whole upgrade again, but still nothing visible.

Rebuilding the indexes now

So was that problem because I forgot to re-index after installing 1T & 1U, or because of the latest version upgrade? If the latter, probably needs adding to the release notes.

Oddly enough Mike, I copied the text of your post above into an email to Purgle and she managed to click the link in the email & open it normally. I assume it is a browser problem then (I am using Firefox)