<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Apr 5, 2014 at 4:31 AM, Mark Perkins <span dir="ltr"><<a href="mailto:perkins1724@hotmail.com" target="_blank">perkins1724@hotmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><div class="h5"><div></div><div>On 5 Apr 2014, at 3:54 pm, "Ian Evans" <<a href="mailto:dheianevans@gmail.com" target="_blank">dheianevans@gmail.com</a>> wrote:<br>
</div><div><span></span></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Apr 5, 2014 at 12:45 AM, Mark Perkins <span dir="ltr"><<a href="mailto:perkins1724@hotmail.com" target="_blank">perkins1724@hotmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I can't for the life of me remember where, but somewhere there is a duplicate detection setting where you can choose to match on previously recorded, current recording, or both (or equivalent wording). If it wasn't updated in oldrecorded as well then you would need to make sure that your duplicate detection settings included checking the recorded table (or else update in oldrecorded as well). May need to check the duplicate flag in both to make sure it is not set to allow re-recording (0=yes, 1=no?) as well.<br>
<div><div><br><br></div></div></blockquote><div>Just looked at the recording rule in mythweb and it's set to check for duplicates in "All Recordings"...so I'm confused as to why it's not catching it then. <br>
</div></div><br></div></div>
</div></blockquote></div></div><blockquote type="cite"><div><span>_______________________________________________</span><br></div></blockquote>It might be worth checking the duplicate flag on the records in both recorded table and oldrecorded table. Perhaps there are some smarts in the code that always set duplicate flag to 0 when a generic programid is found? </div>
<br></blockquote><div><br></div><div>So in other words there's not an easy way to handle this situation without more developer-discouraged futzing with the db. :-(<br><br></div><div>Perhaps I'll drop a line to the channel to see why they can't supply the proper info to Tribune.<br>
</div></div><br></div></div>