chrisspring (25/03/2011) Thanks Dave
I tried a new database but needed an enabler code, so I took a copy of the MDB before and after doing some minor schedule changes. Basically to see what gets changed. I deleted all the entries out of the Logs table with MSAccess and replaced the live MDB with the new on. Then with autotrack I removed from playout then unscheduled everything, Then rescheduled and send to playout. All ok now!
I guess it was do with mixing log entries between different versions of autotrack and/or Myriad
regards ChrisSounds like you've created a new Autotrack Database if it's asking for an enabler code. You want to create a new 'Station Database' - obviously something got corrupted - or at least had an entry which Autorack didn't like. Effectively you've done by a round about method the same - by deleting entries in the database in Access you've forced Myriad / Autotrack to rebuild the tables - I'd have still opted for getting Myriad to create a new database option myself, just to make sure all the correct entries have been created. I've had similar issues in the past when users have tried to push the same schedule period multiple times into a Myriad v2.6 Q-Nxt database (a.k.a. Station Database in v3 parlance), causing all sorts of problems with Myriad and Autotrack getting confused that only creating a new clean schedule database fixed.
-- Myriad user since 1998, now custodian of dozens of Myriad,Autotrack, Powerlog and Scoop boxes of many different flavours. http://www.philedmonds.com
|