Hi

I can't at the moment duplicate this on my test database or on a live database upgraded to v6.29.  Can you confirm that the version of R6 you have loaded is 6,29.0.290 with the database you are up to is 000000BX . The change made was to the update of the settings table. Can you possibly supply a copy of your settings table. If I can't see anything there, I will change the code to see where it is getting to when it hangs.

Thanks. At a first glance I can't see anything which would cause a problem.  I will do some more work on it and get back to you.

Thanks.  I will see what can be done to get around this problem. This code is there, because you can change some aspects of the processing of temporary data in  options.  The first part of the check makes sure that Surveys having unparsed Recorders have the temporary  indicator set to true.  Not having this will cause problems in R6 so this check is in various key places. The concept behind  temporary data is that it is held only for use in the system for reporting purposes and that it should never be distributed as data. It seems strange to me to have a Survey defined as Temporary and yet have  licence to distribute data,.   In what circumstances would you think temporary data could be distributed ?

Understood. There is an issue over data being input to a temporary survey with unparsed names, then the temporary indicator being changed leaving unparsed data on surveys which do not have the indicator set. This causes R6 not to report data correctly and can cause unhandled errors. In trying to deal with it didn't seem sensible to leave these Surveys with licences which allow distribution.  I see that you are using licences in a  much more complex way and that this approach will cause you problems.  I think you have access to Management Studio so as a temporary  measure I suggest that you just alter the procedure to avoid it making the change again. A code change is required to allow you to set up new temporary Surveys with anything other than the 'No rights' licence. I will try to get this done asap, but if it gives you problems I will supply a temporary upgrade. 

ALTER PROCEDURE [dbo].[usp_Setting_Temp_Survey]

AS
   
    UPDATE SURVEY SET Temporary_Survey = 1 WHERE
    EXISTS (SELECT * FROM SAMPLE S INNER JOIN SURVEY_EVENT SE ON
    SE.SURVEY_EVENT_KEY = S.SURVEY_EVENT_KEY INNER JOIN SURVEY SV
    ON SV.SURVEY_KEY = SE.SURVEY_KEY WHERE ISNULL(S.RECORDERS,'') <> ''
    AND SV.SURVEY_KEY = SURVEY.SURVEY_KEY)

Hi

It will be perfectly Ok to make the change.  It will be there for everyone in 6.30 which is nearly ready to go. Implementing the change immediately will not affect the 6.30 upgrade.

Hi,

I saw on http://www.recorder6.info/page26.html that upgrade 6.30.0 will be available shortly (Nov 2019).  I was just wondering if you knew roughly when this might be?  We are currently on 6.28 and as we have to get IT involved to upgrade, which can be time consuming and take a while to be implemented, if we can just ask them to run the 6.30 update in the near future rather than also run the 6.29, that would be useful.  However, if it still might be a few weeks until 6.30 is available, it might be worth asking them to run 6.29 in the interim?

Thanks for any info,
Linds