by Barry4679 » Mon Feb 06, 2017 7:06 am
Ludek wrote:Hi, you seem to be true, the condition ID: 46 is MM5 only, it is a new condition for "Date" format that was previously threated as integer in MM4.
So you are true that adding this condition by MM5 to an auto-playlist causes the auto-playlist be unreadable by MM4.
Thanks, I guess that you may be correct, but that's not as I remember it.
IIRC what happened was:
* the index was created and functional in MM4 ... it was created years ago, hasn't been altered since
* I opened and updated the MM4 db in MM5 unknowingly, due to the bug in the MM5 alpha ... nothing to do with the index .. I just added a few more tracks using MM5 I think
* the index, in
MM4, suddenly started returning unexpected tracks (ie. tracks which had never been played) ... MM4 also got the annoying error 46 error dbox ... I didn't connect these 2 events at the time ... but I started to think that MM5 had some impact on MM4 dlls or something
* I changed the index specification using MM4 ... away from "IS NOT NULL" to "IS > 1/1/1960" ... this fixed the index ... and also seems to have fixed the error dbox problem ... again I didn't recognise the connection, as I was doing a lot of things to try and resolve the problem (ie. db re-orgs ... opening MM4 and opening MM5 at the same time ... then closing MM5 cleanly, then closing MM5 (as I was having quite of few situations where MM5 hung, and had to be killed off by the Task Manage)r, etc etc)
If this the above sequence is correct, the error wasn't created by a change that I made in MM5 ... it was caused by MM5 opening and updating the MM4 db.
[quote="Ludek"]Hi, you seem to be true, the condition ID: 46 is MM5 only, it is a new condition for "Date" format that was previously threated as integer in MM4.
So you are true that adding this condition by MM5 to an auto-playlist causes the auto-playlist be unreadable by MM4.[/quote]
Thanks, I guess that you may be correct, but that's not as I remember it.
IIRC what happened was:
* the index was created and functional in MM4 ... it was created years ago, hasn't been altered since
* I opened and updated the MM4 db in MM5 unknowingly, due to the bug in the MM5 alpha ... nothing to do with the index .. I just added a few more tracks using MM5 I think
* the index, in [u]MM4[/u], suddenly started returning unexpected tracks (ie. tracks which had never been played) ... MM4 also got the annoying error 46 error dbox ... I didn't connect these 2 events at the time ... but I started to think that MM5 had some impact on MM4 dlls or something
* I changed the index specification using MM4 ... away from "IS NOT NULL" to "IS > 1/1/1960" ... this fixed the index ... and also seems to have fixed the error dbox problem ... again I didn't recognise the connection, as I was doing a lot of things to try and resolve the problem (ie. db re-orgs ... opening MM4 and opening MM5 at the same time ... then closing MM5 cleanly, then closing MM5 (as I was having quite of few situations where MM5 hung, and had to be killed off by the Task Manage)r, etc etc)
If this the above sequence is correct, the error wasn't created by a change that I made in MM5 ... it was caused by MM5 opening and updating the MM4 db.