MM 3.0 script changes

[Bex]

For what do you want to use the ODBC driver?

Probably to use it with Access...

[MarineBrat]

For what do you want to use the ODBC driver?

Not for Access. I'm a dBase/xBase geek. I occasionally like to update my Custom3 field based on a string in the path of the song. I use Custom3 for the file source. So for instance, I have a regular weekly download of songs that go into a directory that might look like this...

"C:\My Music\XYZ Downloads\20070404"

The last portion of the song path is the date of download. I would like to place into my Custom3 field the value of "XYZ-20070404". So I have a dBase script do three things. First, it brings the entire songs table down to a dBase file. Second, it globally replaces that dBase table to update whatever fields I want to be updated. Something like...

Filter:
Path contains "XYZ Downloads" and Custom3 is empty.

Replace: Custom3 with an expression that pieces together "XYZ-"+ the proper date string pulled from the path. Or occasionally I might want to globally change the path to songs. You know, whatever needs to be modified.

The third thing in the script is a process that pushes the dBase table back up to the SQL server (oops... Access), matching on SONGS.ID and updating whatever fields I've modified in the dBase file.

It sounds complex but it gets easier after you've done it a few thousand times. And it's just the push of a button.

So actually, to really answer your question I should mention that I do the above to any database that I can access through the Borland Database Engine (BDE). But the BDE does not have a native driver for the new MM SQL engine. But the BDE can also go through an ODBC source. I'm concerned that if the new MediaMonkey SQL engine is done purely in-house then they're going to have to provide something to us, or the only access to the MM data will be through the MM interface or MM scripts.

[Owyn]

FYI: I have been using Sqliteman with the MM3 DB.

The 1.0 stable version does not support IUNICODE but the 1.1 2008-02-20 snapshot (latest available) does.

UI is fairly intuitive, no problems noted once I switched to the snapshot.

http://sqliteman.com/
http://sourceforge.net/project/showfile ... _id=189610

[AllBliss]

I'm a scripter, but in MM3 I'm not sure how to change a song's albumartist.

When I loaded my tracks, MM crazily used a right subset of the Artist as the AlbumArtist (e.g., Davis for Miles Davis)

I'd like to use SQL for the fix.

Do I have to separately update the Songs table (to fix AlbumArtist) and the ArtistsAlbums table?

Has anyone already been here?

[onenonymous]

try SwitchOrCopyFields: Switches or Copies song data fields