Reply to thread

Message

<blockquote data-quote="AmenRa" data-source="post: 497787" data-attributes="member: 54376">I upgraded from 1.0.1.0 to 1.0.2.0.I upgraded the Schedules Direct client as well. I am getting the TV line-up and schedules with no problem.I can no longer access my recorded TV items. Our cable provider just re-mapping all the cable channels. I suspect this might have something to do with it. I had to delete all the channels and download the new line-up.I sure hope the re-mapping of channels has NOTHING to do with what I have recorded - although I suspect it is the problem. Why any programmer would link a recorded media to a channel mapping is beyond me. Doesn't make sense.How do I fix this?Furthermore, a MODAL window pops up with the same error message while running MP.OK, I figured it out.The column idChannel in the recording table must match an entry in the channel table.Piss-poor database implementation. Relating non-volatile data (recording) to volatile data (channel) is bad practice. A person will loose all their recording if they change their channel line-up. For example: Cable company changes the line-up or, you move, or you switch from cable to satellite or vice-versa.</blockquote>

[QUOTE="AmenRa, post: 497787, member: 54376"] I upgraded from 1.0.1.0 to 1.0.2.0. I upgraded the Schedules Direct client as well. I am getting the TV line-up and schedules with no problem. I can no longer access my recorded TV items. Our cable provider just re-mapping all the cable channels. I suspect this might have something to do with it. I had to delete all the channels and download the new line-up. I sure hope the re-mapping of channels has NOTHING to do with what I have recorded - although I suspect it is the problem. Why any programmer would link a recorded media to a channel mapping is beyond me. Doesn't make sense. How do I fix this? Furthermore, a MODAL window pops up with the same error message while running MP. OK, I figured it out. The column [i]idChannel[/i] in the [i]recording[/i] table must match an entry in the [i]channel[/i] table. Piss-poor database implementation. Relating non-volatile data (recording) to volatile data (channel) is bad practice. A person will loose all their recording if they change their channel line-up. For example: Cable company changes the line-up or, you move, or you switch from cable to satellite or vice-versa. [/QUOTE]

Verification