1 Reply by Darwyn Sumner (LERC)

  • Darwyn Sumner (LERC)
  • Veteran
  • Offline
  • Registered: 07-06-2006
  • Posts: 176

Re: A cautionary tale

I managed to completely exclude myself from my own laptop version of Recorder, you can reproduce this as follows:

1. Ensure that you are the only registered user of Recorder (i.e. delete Default User)
2. Ensure that there are two versions of yourself in the Names and Addresses module
3. Merge the version of you that is the System Manager with the version of you that is not even registered as a user
4. Exit Recorder and try to get in again :D

I got back in - I would be interested in hearing of other people's solutions (theoretical ones of course)

Don't try this at home unless you are really certain you can restore your access

P.S. It might just be worth a bit of an adjustment to the way that the merge facility works to prevent this

2 Reply by ILawrie

  • ILawrie
  • Member
  • Offline
  • Registered: 10-11-2006
  • Posts: 22

Re: A cautionary tale

Hi Darwyn

For what it's worth I'd change the security level to 5 using SQL Server Management Studio Express and that should straighten everything out - that's possibly how you did recover this?

Iain

3 Reply by charlesroper

  • charlesroper
  • charlesroper
  • Digital Development Manager
  • Offline
  • From: Field Studies Council
  • Registered: 26-03-2006
  • Posts: 906

Re: A cautionary tale

Yes, I'd find the NAME_KEY for my (new) self or some other individual I wanted to add as a USER:

USE NBNData;
SELECT 
    name_key
    ,forename
    ,surname
FROM
    individual
WHERE
    surname = 'roper'

Then add the relevant user to the USER table:

USE NBNData;
INSERT INTO [user] VALUES(N'XXXXXXXXXXXXXXXX', N'password', 5, 'True', 'False');

Where XXXXXXXXXXXXXXXX is the NAME_KEY you looked up in the previous query.

Charles Roper
Digital Development Manager | Field Studies Council
http://www.field-studies-council.org | https://twitter.com/charlesroper | https://twitter.com/fsc_digital

charlesroper's Website