MediaMonkey Wiki - User contributions [en]

Introduction to scripting

2007-10-10T21:50:05Z

Imd1b4u: /* Considerations */ Fixed up point about database

MediaMonkey can be customized through the use of custom scripts. Scripts are relatively simple computer programs written in a scripting language, such as VBScript. Unlike most computer programs, these scripts do not have to be compiled, which allows them to be tested and modified more easily than with more advanced languages. Still, writing MediaMonkey scripts can be a challenging experience so potential script writers should consider alternatives, particularly if they have little previous experience writing scripts.

== Considerations ==

Before writing their own scripts, users of MediaMonkey may wish to consider the following issues:
*In addition to supporting scripting, MediaMonkey has a [[Plug-ins|plug-in]] interface that allows a large number of Winamp and MediaMonkey plug-ins to be used. There may be no need to write a script if the desired features are already provided by a plug-in.
*Some users of MediaMonkey are willing to share the scripts that they have written with other users. An existing script may already provide the desired features or be relatively easily modified so that it does. The best place to find such scripts or to get support for them is the [http://www.mediamonkey.com/forum/viewforum.php?f=2 Scripts and Components forum].
*Although, in theory, MediaMonkey supports both of the [http://en.wikipedia.org/wiki/VBScript VBScript] (*.vbs) and [http://en.wikipedia.org/wiki/JScript JScript] (*.js) scripting languages, the implementation for JScript is only partial, so only VBScript can be used for some purposes. Programmers not wishing to deal with the idiosyncrasies of VBScript may wish to create an [[#About external scripts and applications |external]] script or application using their preferred language and use a script written in VBScript (or JScript) to launch it.
*MediaMonkey’s [http://en.wikipedia.org/wiki/Application_programming_interface Application Programming Interface] (API) is somewhat poorly designed and its implementation is rather buggy. The official documentation for it is very limited and occasionally misleading or incorrect. Some users of MediaMonkey are attempting to provide [[Scripting|more information]] in this wiki, but little has been written yet. Some people with scripting experience are willing to help others in the [http://www.mediamonkey.com/forum/viewforum.php?f=2 Scripts and Components forum] and scripts already written by others can serve as examples. Still, a considerable amount of trial-and-error is necessary to develop an understanding of the MediaMonkey scripting API.
*Other than tags embedded in media files, virtually all of MediaMonkey’s data is stored in a [http://en.wikipedia.org/wiki/Microsoft_Jet_Database_Engine Microsoft Jet] relational database by MediaMonkey 2.x, while MediaMonkey 3.x uses a [http://www.sqlite.org SQLite] database. It is possible to manipulate MediaMonkey’s data, while minimizing the use of MediaMonkey’s API, by using [http://en.wikipedia.org/wiki/SQL SQL]. MediaMonkey's API can be completely bypassed by using an interface provided by the underlying engine to access the database. MediaMonkey 2.x’s database can accessed through Jet or ODBC, or even opened directly by Microsoft Access, for example.

== Types of scripts ==

There are three major types of scripts that can be launched internally by MediaMonkey:
*'''Normal scripts''' are located in the ''Scripts'' folder and are executed according to the script's entry in the [[#Format of the Scripts.ini file|''Scripts\Scripts.ini'' file]].
*'''Auto-scripts''' are located in the ''Scripts\Auto'' folder and its OnStartup method is executed when MediaMonkey starts.
*'''Other scripts''', such as [[Search scripts]] and [[Auto-DJ scripts]] are intended for specific types of customization, but are also defined in the [[#Format of the Scripts.ini file|''Scripts\Scripts.ini'' file]].

In addition to the scripts that are launched by MediaMonkey (internal scripts), you can also work with MediaMonkey by using [[#About external scripts and applications|''external'' scripts and applications]].

== How to create a normal script ==

<ol>
<li>Create a plain text file in the ''Scripts'' folder, e.g. ''MyNormalScript.vbs''.</li>
<li>Write your VBScript script and make sure you have a procedure that can be called, e.g.
<source lang="vb">Sub CallMe

' This script will pop up a simple message box when the procedure CallMe is called.
MsgBox "CallMe was called by the action defined in the Scripts.ini file."

End Sub</source></li>
<li>Create a new entry for your script's ''CallMe'' procedure in the [[#Format of the Scripts.ini file|''Scripts.ini'' file]].</li>
</ol>

From within a MediaMonkey script, a reference to the SDB object (an instance of the [[SDBApplication]] class) is always present. By accessing its properties and methods, you can interact with many aspects of MediaMonkey. Check out the [[MediaMonkey Automation objects]] page for other MediaMonkey objects that can be created starting from the SDB object.
Another available object reference is the Script object (an instance of the [[SDBScriptControl]] class), that contains methods to control the running script's environment, usually to [[ISDBScriptControl::RegisterEvent|attach]] to events of MediaMonkey and its player and controls (see examples [[Sample Event Handlers script|1]] and [[Sample Events for User Interface script|2]]).

The script ''Scripts\MediaMonkey init.vbs'' is always executed just before any other script. It contains some constants that can be used in your own script.

A good and quite complex example is ''Scripts\Export.vbs'' (distributed with MediaMonkey) which contains code that takes care of all export features of MediaMonkey. For more examples, check out the [[Sample scripts|sample scripts page]].

More information about scripting in general can be found at [http://msdn2.microsoft.com/en-us/library/ms950396.aspx Microsoft Scripting] (with official VBScript and JScript documentation).

== How to create an auto-script ==

<ol>
<li>Create a plain text file in the ''Scripts\Auto'' folder, e.g. ''MyAutoScript.vbs''.</li>
<li>Write your VBScript script and use the procedure ''OnStartup'' as start point for execution, e.g.
<source lang="vb">
Sub OnStartup

' This script will pop up a simple "Hello World!" message box when you start MediaMonkey.
MsgBox "Hello World!"

End Sub
</source></li>
</ol>

All VBScript, but not JScript, scripts in the ''Scripts\Auto'' folder are automatically checked during MM start-up, and the '''OnStartup''' procedure (if present) is called. Auto-scripts make it possible to add user interface enhancements such as new menu or toolbar items, new option sheets, etc.

Except that these scripts are automatically executed when MediaMonkey starts, they behave identical as the normal scripts. They also get a reference to the SDB object, and the constants defined in ''Scripts\MediaMonkey init.vbs'' are always usable.

== Format of the ''Scripts.ini'' file ==

<div style="float: right; margin-left: 1em; margin-bottom: 0.5em; clear: right; background-color:#F9F9F9; border:1px solid #CCCCCC; font-size:95%; padding:5px;">
<source lang="ini">
[AutoIncTrackN]
FileName=AutoIncTrackN.vbs
ProcName=AutoIncTrackNumbers
Order=1
DisplayName=Auto-&increment Track #s...
Description=Sequentially numbers Tracks
Language=VBScript
ScriptType=0
</source>
<div style="position: relative; top: -6px; left: 5px">Sample ''Scripts.ini'' entry</div>
</div>

This ''Scripts\Scripts.ini'' file is a standard .ini file where each section defines a procedure in a script. The section starts with a section identifier [SectionName], where ‘SectionName’ is a unique name of the script entry.
These are the entry's properties:
; Filename
: Path of a script file where the procedure is located, relative to the ''Scripts'' folder, e.g. ‘MyScripts.vbs’.
; ProcName
: Name of an existing procedure to be called when the script (specifiedby ‘Filename’) is executed in MM.
; ScriptType
: Defines type of the script:
:* 0 = A ''standard script'' that appears in the <code>Tools > Scripts</code> submenu.
:* 1 = An ''export script'' that can be found in the <code>File > Export</code> submenu.
:* 2 = A ''track-start script'' that is activated whenever a new track is started. This script doesn’t appear in any menu, it’s simply called in the background. When this procedure is executed, a variable 'CurrentTrack' (object of the [[SDBSongData]] class) is defined, and you can use it to get information about the started track.
:* 3 = A ''search script'' that allows custom searches to be programmed in the "Auto-tag from Web" dialog. See [[Search scripts]] for more information about this more complex script type.
:* 4 = An ''Auto-DJ script'' that can handle content added by Auto-DJ. See [[Auto-DJ scripts]] for more details.
; Order
: Defines the order of the script in its section. These numbers are sorted and scripts are listed according to the order.
; DisplayName
: The script is listed as menu item with this name.
; Description
: Message shown as tooltip when the mouse is moved over the menu item.
; Language
: The script language of the referenced script. Usually VBScript, but can be JScript too (although this is not recommended).
; Shortcut
: Specifies a shortcut that invokes the script in MM. You can use any of the strings ‘Shift+’, ‘Ctrl+’ or ‘Alt+’, even combined together and followed either by a single letter or a special key (BkSp, Tab, Enter, Esc, Space, PgUp, PgDn, End, Home, Left, Up, Right, Down, Ins, Del).

== About external scripts and applications ==

External scripts are launched from outside MediaMonkey. They can be scripts that are started by a MediaMonkey script (e.g. ''helper scripts''), or that originated outside MediaMonkey (regular *.vbs scripts, local html pages, ASP server pages, ...). The same situation applies to applications that are not a part of MediaMonkey, but which use its COM object (the COM and the scripting API are the same).

In order to work with MediaMonkey’s objects from outside a MediaMonkey script, you need to create a reference to the SDB object (an instance of the [[SDBApplication]] class) yourself. For external applications, make sure that you have added a reference to the SongsDB library, first.

If MediaMonkey is already running, a call to the SDB object will return a reference to the running instance. If MediaMonkey is not running yet, it will be started and a reference will be returned. In addition, if MediaMonkey was was not running before, it will normally shut down automatically when the external script/application exits. This can be prevented (MediaMonkey will remain running) by setting SDB's [[ISDBApplication::ShutdownAfterDisconnect|ShutdownAfterDisconnect]] property to False.

'''Visual Basic / VBScript sample:'''
<source lang="vb">
Dim SDB : Set SDB = CreateObject("SongsDB.SDBApplication")

SDB.ShutdownAfterDisconnect = False ' in case you want to keep an opened instance open after disconnecting the SDB object
</source>
'''C# sample:'''
<source lang="csharp">
SongsDB.SDBApplicationClass SDB = new SongsDB.SDBApplicationClass();

SDB.ShutdownAfterDisconnect = false; // in case you want to keep an opened instance open after disconnecting the SDB object
</source>

'''Delphi sample:'''
<source lang="delphi">
var
SDB : Variant;
begin
SDB := CreateObject('SongsDB.SDBApplication');
SDB.ShutdownAfterDisconnect := false; // in case you want to keep an opened instance open after disconnecting the SDB object
</source>

'''PHP sample:''' (shows initialization only)
<source lang="php">
$objSDB = new COM('SongsDB.SDBApplication') or die('Cannot create MediaMonkey SDB Object');
</source>

Introduction to scripting

2007-10-10T21:06:13Z

Imd1b4u: New Introduction and Considerations plus minor stuff

MediaMonkey can be customized through the use of custom scripts. Scripts are relatively simple computer programs written in a scripting language, such as VBScript. Unlike most computer programs, these scripts do not have to be compiled, which allows them to be tested and modified more easily than with more advanced languages. Still, writing MediaMonkey scripts can be a challenging experience so potential script writers should consider alternatives, particularly if they have little previous experience writing scripts.

== Considerations ==

Before writing their own scripts, users of MediaMonkey may wish to consider the following issues:
*In addition to supporting scripting, MediaMonkey has a [[Plug-ins|plug-in]] interface that allows a large number of Winamp and MediaMonkey plug-ins to be used. There may be no need to write a script if the desired features are already provided by a plug-in.
*Some users of MediaMonkey are willing to share the scripts that they have written with other users. An existing script may already provide the desired features or be relatively easily modified so that it does. The best place to find such scripts or to get support for them is the [http://www.mediamonkey.com/forum/viewforum.php?f=2 Scripts and Components forum].
*Although, in theory, MediaMonkey supports both of the [http://en.wikipedia.org/wiki/VBScript VBScript] (*.vbs) and [http://en.wikipedia.org/wiki/JScript JScript] (*.js) scripting languages, the implementation for JScript is only partial, so only VBScript can be used for some purposes. Programmers not wishing to deal with the idiosyncrasies of VBScript may wish to create an [[#About external scripts and applications |external]] script or application using their preferred language and use a script written in VBScript (or JScript) to launch it.
*MediaMonkey’s [http://en.wikipedia.org/wiki/Application_programming_interface Application Programming Interface] (API) is somewhat poorly designed and its implementation is rather buggy. The official documentation for it is very limited and occasionally misleading or incorrect. Some users of MediaMonkey are attempting to provide [[Scripting|more information]] in this wiki, but little has been written yet. Some people with scripting experience are willing to help others in the [http://www.mediamonkey.com/forum/viewforum.php?f=2 Scripts and Components forum] and scripts already written by others can serve as examples. Still, a considerable amount of trial-and-error is necessary to develop an understanding of the MediaMonkey scripting API.
*Other than tags embedded in media files, virtually all of MediaMonkey’s data is stored in a [http://en.wikipedia.org/wiki/Microsoft_Jet_Database_Engine Microsoft Jet] relational database by MediaMonkey 2.x, while MediaMonkey 3.x uses a [http://www.sqlite.org SQLite] database. It is possible to manipulate MediaMonkey’s database, while avoiding or minimizing the use of MediaMonkey’s API, by using [http://en.wikipedia.org/wiki/SQL SQL]. SQL statements and queries can be directed at the database through MediaMonkey’s API or some other interface. MediaMonkey 2.x’s database can accessed through Jet or ODBC, or even opened directly by Microsoft Access, for example.

== Types of scripts ==

There are three major types of scripts that can be launched internally by MediaMonkey:
*'''Normal scripts''' are located in the ''Scripts'' folder and are executed according to the script's entry in the [[#Format of the Scripts.ini file|''Scripts\Scripts.ini'' file]].
*'''Auto-scripts''' are located in the ''Scripts\Auto'' folder and its OnStartup method is executed when MediaMonkey starts.
*'''Other scripts''', such as [[Search scripts]] and [[Auto-DJ scripts]] are intended for specific types of customization, but are also defined in the [[#Format of the Scripts.ini file|''Scripts\Scripts.ini'' file]].

In addition to the scripts that are launched by MediaMonkey (internal scripts), you can also work with MediaMonkey by using [[#About external scripts and applications|''external'' scripts and applications]].

== How to create a normal script ==

<ol>
<li>Create a plain text file in the ''Scripts'' folder, e.g. ''MyNormalScript.vbs''.</li>
<li>Write your VBScript script and make sure you have a procedure that can be called, e.g.
<source lang="vb">Sub CallMe

' This script will pop up a simple message box when the procedure CallMe is called.
MsgBox "CallMe was called by the action defined in the Scripts.ini file."

End Sub</source></li>
<li>Create a new entry for your script's ''CallMe'' procedure in the [[#Format of the Scripts.ini file|''Scripts.ini'' file]].</li>
</ol>

From within a MediaMonkey script, a reference to the SDB object (an instance of the [[SDBApplication]] class) is always present. By accessing its properties and methods, you can interact with many aspects of MediaMonkey. Check out the [[MediaMonkey Automation objects]] page for other MediaMonkey objects that can be created starting from the SDB object.
Another available object reference is the Script object (an instance of the [[SDBScriptControl]] class), that contains methods to control the running script's environment, usually to [[ISDBScriptControl::RegisterEvent|attach]] to events of MediaMonkey and its player and controls (see examples [[Sample Event Handlers script|1]] and [[Sample Events for User Interface script|2]]).

The script ''Scripts\MediaMonkey init.vbs'' is always executed just before any other script. It contains some constants that can be used in your own script.

A good and quite complex example is ''Scripts\Export.vbs'' (distributed with MediaMonkey) which contains code that takes care of all export features of MediaMonkey. For more examples, check out the [[Sample scripts|sample scripts page]].

More information about scripting in general can be found at [http://msdn2.microsoft.com/en-us/library/ms950396.aspx Microsoft Scripting] (with official VBScript and JScript documentation).

== How to create an auto-script ==

<ol>
<li>Create a plain text file in the ''Scripts\Auto'' folder, e.g. ''MyAutoScript.vbs''.</li>
<li>Write your VBScript script and use the procedure ''OnStartup'' as start point for execution, e.g.
<source lang="vb">
Sub OnStartup

' This script will pop up a simple "Hello World!" message box when you start MediaMonkey.
MsgBox "Hello World!"

End Sub
</source></li>
</ol>

All VBScript, but not JScript, scripts in the ''Scripts\Auto'' folder are automatically checked during MM start-up, and the '''OnStartup''' procedure (if present) is called. Auto-scripts make it possible to add user interface enhancements such as new menu or toolbar items, new option sheets, etc.

Except that these scripts are automatically executed when MediaMonkey starts, they behave identical as the normal scripts. They also get a reference to the SDB object, and the constants defined in ''Scripts\MediaMonkey init.vbs'' are always usable.

== Format of the ''Scripts.ini'' file ==

<div style="float: right; margin-left: 1em; margin-bottom: 0.5em; clear: right; background-color:#F9F9F9; border:1px solid #CCCCCC; font-size:95%; padding:5px;">
<source lang="ini">
[AutoIncTrackN]
FileName=AutoIncTrackN.vbs
ProcName=AutoIncTrackNumbers
Order=1
DisplayName=Auto-&increment Track #s...
Description=Sequentially numbers Tracks
Language=VBScript
ScriptType=0
</source>
<div style="position: relative; top: -6px; left: 5px">Sample ''Scripts.ini'' entry</div>
</div>

This ''Scripts\Scripts.ini'' file is a standard .ini file where each section defines a procedure in a script. The section starts with a section identifier [SectionName], where ‘SectionName’ is a unique name of the script entry.
These are the entry's properties:
; Filename
: Path of a script file where the procedure is located, relative to the ''Scripts'' folder, e.g. ‘MyScripts.vbs’.
; ProcName
: Name of an existing procedure to be called when the script (specifiedby ‘Filename’) is executed in MM.
; ScriptType
: Defines type of the script:
:* 0 = A ''standard script'' that appears in the <code>Tools > Scripts</code> submenu.
:* 1 = An ''export script'' that can be found in the <code>File > Export</code> submenu.
:* 2 = A ''track-start script'' that is activated whenever a new track is started. This script doesn’t appear in any menu, it’s simply called in the background. When this procedure is executed, a variable 'CurrentTrack' (object of the [[SDBSongData]] class) is defined, and you can use it to get information about the started track.
:* 3 = A ''search script'' that allows custom searches to be programmed in the "Auto-tag from Web" dialog. See [[Search scripts]] for more information about this more complex script type.
:* 4 = An ''Auto-DJ script'' that can handle content added by Auto-DJ. See [[Auto-DJ scripts]] for more details.
; Order
: Defines the order of the script in its section. These numbers are sorted and scripts are listed according to the order.
; DisplayName
: The script is listed as menu item with this name.
; Description
: Message shown as tooltip when the mouse is moved over the menu item.
; Language
: The script language of the referenced script. Usually VBScript, but can be JScript too (although this is not recommended).
; Shortcut
: Specifies a shortcut that invokes the script in MM. You can use any of the strings ‘Shift+’, ‘Ctrl+’ or ‘Alt+’, even combined together and followed either by a single letter or a special key (BkSp, Tab, Enter, Esc, Space, PgUp, PgDn, End, Home, Left, Up, Right, Down, Ins, Del).

== About external scripts and applications ==

External scripts are launched from outside MediaMonkey. They can be scripts that are started by a MediaMonkey script (e.g. ''helper scripts''), or that originated outside MediaMonkey (regular *.vbs scripts, local html pages, ASP server pages, ...). The same situation applies to applications that are not a part of MediaMonkey, but which use its COM object (the COM and the scripting API are the same).

In order to work with MediaMonkey’s objects from outside a MediaMonkey script, you need to create a reference to the SDB object (an instance of the [[SDBApplication]] class) yourself. For external applications, make sure that you have added a reference to the SongsDB library, first.

If MediaMonkey is already running, a call to the SDB object will return a reference to the running instance. If MediaMonkey is not running yet, it will be started and a reference will be returned. In addition, if MediaMonkey was was not running before, it will normally shut down automatically when the external script/application exits. This can be prevented (MediaMonkey will remain running) by setting SDB's [[ISDBApplication::ShutdownAfterDisconnect|ShutdownAfterDisconnect]] property to False.

'''Visual Basic / VBScript sample:'''
<source lang="vb">
Dim SDB : Set SDB = CreateObject("SongsDB.SDBApplication")

SDB.ShutdownAfterDisconnect = False ' in case you want to keep an opened instance open after disconnecting the SDB object
</source>
'''C# sample:'''
<source lang="csharp">
SongsDB.SDBApplicationClass SDB = new SongsDB.SDBApplicationClass();

SDB.ShutdownAfterDisconnect = false; // in case you want to keep an opened instance open after disconnecting the SDB object
</source>

'''Delphi sample:'''
<source lang="delphi">
var
SDB : Variant;
begin
SDB := CreateObject('SongsDB.SDBApplication');
SDB.ShutdownAfterDisconnect := false; // in case you want to keep an opened instance open after disconnecting the SDB object
</source>

'''PHP sample:''' (shows initialization only)
<source lang="php">
$objSDB = new COM('SongsDB.SDBApplication') or die('Cannot create MediaMonkey SDB Object');
</source>

ISDBSongData::Author

2007-10-10T16:54:32Z

Imd1b4u: /* Property description */ Changed wording of my previous edit

{{MethodDeclaration|SDBSongData|ISDBSongData|Property Get/Let Author As String}}

===Property description===

There is a redundant property, [[ISDBSongData::MusicComposer]], in Media Monkey 2.5. Based on limited testing it appears that this property (Author) is the property to use. The [[ISDBSongData::UpdateDB]] and [[ISDBSongData::WriteTags]] methods seem to use the value from Author rather than the value in the [[ISDBSongData::MusicComposer]] property. Also, this value can be used to display data already in the database, while [[ISDBSongData::MusicComposer]] apparently does not.

The situation under MediaMonkey version 3.x is unknown.

[[Category:Scripting|{{PAGENAME}}]]
[[Category:Automation objects|{{PAGENAME}}]]
[[Category:CoClass SDBSongData|{{PAGENAME}}]]
[[Category:Interface ISDBSongData|{{PAGENAME}}]]

ISDBSongData::Author

2007-10-10T16:48:06Z

Imd1b4u: /* Property description */ Changed wording of my previous edit

{{MethodDeclaration|SDBSongData|ISDBSongData|Property Get/Let Author As String}}

===Property description===

There is a redundant property, [[ISDBSongData::MusicComposer]], in Media Monkey 2.5. Based on limited testing it appears that Author is the property to use. The [[ISDBSongData::UpdateDB]] and [[ISDBSongData::WriteTags]] use the value from Author, not the value in the [[ISDBSongData::MusicComposer]] property. Also, this value can be used to display data already in the database, while [[ISDBSongData::MusicComposer]] apparently does not.

The situation under MediaMonkey version 3.x is unknown.

[[Category:Scripting|{{PAGENAME}}]]
[[Category:Automation objects|{{PAGENAME}}]]
[[Category:CoClass SDBSongData|{{PAGENAME}}]]
[[Category:Interface ISDBSongData|{{PAGENAME}}]]

Database Structure

2007-10-10T07:08:37Z

Imd1b4u: /* AddSongInfo */ Cleaned up my previous edit

{{DatabaseTablesList}}

== Database type ==
[http://www.sqlite.org SQLite] version 3
* Encoding: UTF-16le
* Text collate IUNICODE (except where indicated with a (*))

== Database location ==
'''Windows XP:''' C:\Documents and Settings\<USERNAME>\Local Settings\Application Data\MediaMonkey\MM.DB
<br>'''Windows Vista:''' C:\Users\<USERNAME>\AppData\Local\MediaMonkey\MM.DB

== Used data types ==
'''INTEGER''' The value is a signed integer, stored in 1, 2, 3, 4, 6, or 8 bytes depending on the magnitude of the value.
<br>'''REAL''' The value is a floating point value, stored as an 8-byte IEEE floating point number.
<br>'''TEXT''' The value is a text string, stored using the database encoding (UTF-16-LE).

== Structure explanation ==
The most important table is the ''Songs'' table, which is the starting point for all song-specific info. To allow rapid requests, most of the information is present in the table itself, e.g. the Artist name is spelled out.
The link between table Songs and other tables like Artists, Albums, ... happens with intermediary tables, e.g. ArtistsSongs. This allows us to assign multiple songs to one artist, AND multiple artists to one song.

The database contains custom events, called "triggers", that are executed when e.g. an artist is assigned to a track. For that example, the trigger will automatically increment the Artists table's Tracks counter field.

== Database tables ==
*[[Albums table|Albums]]: All info about a certain album.
*[[Artists table|Artists]]
*[[ArtistsAlbums table|ArtistsAlbums]]
*[[ArtistsSongs table|ArtistsSongs]]
*[[Covers table|Covers]]
*[[DBInfo table|DBInfo]]
*[[DeviceFilters table|DeviceFilters]]
*[[DeviceTracks table|DeviceTracks]]
*[[Devices table|Devices]]
*[[Filters table|Filters]]
*[[Folders table|Folders]]
*[[FoldersHier table|FoldersHier]]
*[[Genres table|Genres]]
*[[GenresSongs table|GenresSongs]]
*[[LastTreePath table|LastTreePath]]
*[[Lists table|Lists]]
*[[ListsSongs table|ListsSongs]]
*[[Medias table|Medias]]
*[[OrganizeRules table|OrganizeRules]]
*[[PathProcessing table|PathProcessing]]
*[[Played table|Played]]
*[[PlaylistSongs table|PlaylistSongs]]
*[[Playlists table|Playlists]]
*[[PodcastDirs table|PodcastDirs]]
*[[PodcastEpisodes table|PodcastEpisodes]]
*[[Podcasts table|Podcasts]]
*[[Songs table|Songs]]
*[[SynchAlbum table|SynchAlbum]]
*[[SynchArtist table|SynchArtist]]
*[[SynchLocation table|SynchLocation]]
*[[SynchPlaylist table|SynchPlaylist]]
*[[SynchPodcast table|SynchPodcast]]

----

----

==MediaMonkey v2.5 and lower==

===Database structure===
[[Image:DatabaseRelationsMM2.gif|center|650px]]

===AddSongInfo===
''Value field is "TextData"''

'''DataType'''
{| border="2"
|-
! Value || AIF Code || Description
|-
| 100 || AIF_COPYRIGHT || Copyright
|-
| 101 || AIF_PUBLISHER || Publisher
|-
| 102 || AIF_ENCODER || Encoder
|-
| 103 || AIF_ENCODEDBY || Encoded By
|-
| 200 || AIF_LYRICIST || Lyricist
|-
| 201 || AIF_BAND || Band
|-
| 202 || AIF_CONDUCTOR || Conductor
|-
| 203 || AIF_REMIXER || Remixer
|-
| 204 || AIF_INVOLVEDPEOPLE || Involved People
|-
| 205 || AIF_MUSICCOMPOSER || (See note)
|-
| 300 || AIF_ORIGTITLE || Original Title
|-
| 301 || AIF_ORIGARTIST || Original Artist
|-
| 302 || AIF_ORIGLYRICIST || Original Lyricist
|-
| 400 || AIF_GROUPDESC ||
|-
| 401 || AIF_SUBTITLE ||
|-
| 402 || AIF_ISRC ||
|-
| 500 || AIF_INITIALKEY ||
|-
| 501 || AIF_LANGUAGE ||
|-
| 502 || AIF_MEDIATYPE ||
|-
| 503 || AIF_RATINGSTRING ||
|-
| 1000 || AIF_WEB_COMMERCIAL ||
|-
| 1001 || AIF_WEB_COPYRIGHT ||
|-
| 1002 || AIF_WEB_FILEPAGE ||
|-
| 1003 || AIF_WEB_ARTIST ||
|-
| 1004 || AIF_WEB_SOURCE ||
|-
| 1005 || AIF_WEB_RADIO ||
|-
| 1006 || AIF_WEB_PAYMENT ||
|-
| 1007 || AIF_WEB_PUBLISHER ||
|-
| 1100 || AIF_WEB_USER ||
|}

Note: Apparently, the value for the composer is stored in the Author field of the Songs table rather than in the AddSongInfo table under MediaMonkey 2.5. The situation in other versions is unknown.

===AddSongInfoInt===
''Value field is "IntData"'' (linked to Lists.ID)

'''DataType''' (partially linked to Lists.IDListType)
{| border="2"
|-
! Value || AIF Code || Description
|-
| 10000 || AIF_ORIGYEAR || Original Year
|-
| 10101 || AIF_TEMPO || Tempo
|-
| 10102 || AIF_MOOD || Mood
|-
| 10103 || AIF_OCCASION || Occasion
|-
| 10104 || AIF_QUALITY || Quality
|}
<references/>

===Memos===
''Value field is "MemoText"''

'''MemoType'''
{| border="2"
|-
! Value || AIF Code || Description
|-
| 20000 || AIF_LYRICS || Lyrics
|-
| 20001 || AIF_COMMENT || Comment
|}

Database Structure

2007-10-10T07:07:14Z

Imd1b4u: /* AddSongInfo */ Note about how Composer is stored in MM2

{{DatabaseTablesList}}

== Database type ==
[http://www.sqlite.org SQLite] version 3
* Encoding: UTF-16le
* Text collate IUNICODE (except where indicated with a (*))

== Database location ==
'''Windows XP:''' C:\Documents and Settings\<USERNAME>\Local Settings\Application Data\MediaMonkey\MM.DB
<br>'''Windows Vista:''' C:\Users\<USERNAME>\AppData\Local\MediaMonkey\MM.DB

== Used data types ==
'''INTEGER''' The value is a signed integer, stored in 1, 2, 3, 4, 6, or 8 bytes depending on the magnitude of the value.
<br>'''REAL''' The value is a floating point value, stored as an 8-byte IEEE floating point number.
<br>'''TEXT''' The value is a text string, stored using the database encoding (UTF-16-LE).

== Structure explanation ==
The most important table is the ''Songs'' table, which is the starting point for all song-specific info. To allow rapid requests, most of the information is present in the table itself, e.g. the Artist name is spelled out.
The link between table Songs and other tables like Artists, Albums, ... happens with intermediary tables, e.g. ArtistsSongs. This allows us to assign multiple songs to one artist, AND multiple artists to one song.

The database contains custom events, called "triggers", that are executed when e.g. an artist is assigned to a track. For that example, the trigger will automatically increment the Artists table's Tracks counter field.

== Database tables ==
*[[Albums table|Albums]]: All info about a certain album.
*[[Artists table|Artists]]
*[[ArtistsAlbums table|ArtistsAlbums]]
*[[ArtistsSongs table|ArtistsSongs]]
*[[Covers table|Covers]]
*[[DBInfo table|DBInfo]]
*[[DeviceFilters table|DeviceFilters]]
*[[DeviceTracks table|DeviceTracks]]
*[[Devices table|Devices]]
*[[Filters table|Filters]]
*[[Folders table|Folders]]
*[[FoldersHier table|FoldersHier]]
*[[Genres table|Genres]]
*[[GenresSongs table|GenresSongs]]
*[[LastTreePath table|LastTreePath]]
*[[Lists table|Lists]]
*[[ListsSongs table|ListsSongs]]
*[[Medias table|Medias]]
*[[OrganizeRules table|OrganizeRules]]
*[[PathProcessing table|PathProcessing]]
*[[Played table|Played]]
*[[PlaylistSongs table|PlaylistSongs]]
*[[Playlists table|Playlists]]
*[[PodcastDirs table|PodcastDirs]]
*[[PodcastEpisodes table|PodcastEpisodes]]
*[[Podcasts table|Podcasts]]
*[[Songs table|Songs]]
*[[SynchAlbum table|SynchAlbum]]
*[[SynchArtist table|SynchArtist]]
*[[SynchLocation table|SynchLocation]]
*[[SynchPlaylist table|SynchPlaylist]]
*[[SynchPodcast table|SynchPodcast]]

----

----

==MediaMonkey v2.5 and lower==

===Database structure===
[[Image:DatabaseRelationsMM2.gif|center|650px]]

===AddSongInfo===
''Value field is "TextData"''

'''DataType'''
{| border="2"
|-
! Value || AIF Code || Description
|-
| 100 || AIF_COPYRIGHT || Copyright
|-
| 101 || AIF_PUBLISHER || Publisher
|-
| 102 || AIF_ENCODER || Encoder
|-
| 103 || AIF_ENCODEDBY || Encoded By
|-
| 200 || AIF_LYRICIST || Lyricist
|-
| 201 || AIF_BAND || Band
|-
| 202 || AIF_CONDUCTOR || Conductor
|-
| 203 || AIF_REMIXER || Remixer
|-
| 204 || AIF_INVOLVEDPEOPLE || Involved People
|-
| 205 || AIF_MUSICCOMPOSER || See note
|-
| 300 || AIF_ORIGTITLE || Original Title
|-
| 301 || AIF_ORIGARTIST || Original Artist
|-
| 302 || AIF_ORIGLYRICIST || Original Lyricist
|-
| 400 || AIF_GROUPDESC ||
|-
| 401 || AIF_SUBTITLE ||
|-
| 402 || AIF_ISRC ||
|-
| 500 || AIF_INITIALKEY ||
|-
| 501 || AIF_LANGUAGE ||
|-
| 502 || AIF_MEDIATYPE ||
|-
| 503 || AIF_RATINGSTRING ||
|-
| 1000 || AIF_WEB_COMMERCIAL ||
|-
| 1001 || AIF_WEB_COPYRIGHT ||
|-
| 1002 || AIF_WEB_FILEPAGE ||
|-
| 1003 || AIF_WEB_ARTIST ||
|-
| 1004 || AIF_WEB_SOURCE ||
|-
| 1005 || AIF_WEB_RADIO ||
|-
| 1006 || AIF_WEB_PAYMENT ||
|-
| 1007 || AIF_WEB_PUBLISHER ||
|-
| 1100 || AIF_WEB_USER ||
|}

Note: Apparently, the value for the composer is stored in the Author field of the Songs table rather than in the AddSongInfo table under MediaMonkey 2.5. The situation in other versions is unknown.

===AddSongInfoInt===
''Value field is "IntData"'' (linked to Lists.ID)

'''DataType''' (partially linked to Lists.IDListType)
{| border="2"
|-
! Value || AIF Code || Description
|-
| 10000 || AIF_ORIGYEAR || Original Year
|-
| 10101 || AIF_TEMPO || Tempo
|-
| 10102 || AIF_MOOD || Mood
|-
| 10103 || AIF_OCCASION || Occasion
|-
| 10104 || AIF_QUALITY || Quality
|}
<references/>

===Memos===
''Value field is "MemoText"''

'''MemoType'''
{| border="2"
|-
! Value || AIF Code || Description
|-
| 20000 || AIF_LYRICS || Lyrics
|-
| 20001 || AIF_COMMENT || Comment
|}

ISDBSongData::Author

2007-10-10T06:56:48Z

Imd1b4u: /* Property description */ Documented relation with MusicComposer

{{MethodDeclaration|SDBSongData|ISDBSongData|Property Get/Let Author As String}}

===Property description===

This property has a redundant property, [[ISDBSongData::MusicComposer]], under Media Monkey 2.5. Based on limited testing it appears that Author is the property to use. The [[ISDBSongData::UpdateDB]] and [[ISDBSongData::WriteTags]] write the value from this property, not the value in the [[ISDBSongData::MusicComposer]] property. Also, this value can be used to display data already in the database, while [[ISDBSongData::MusicComposer]] apparently can not.

The situation under MediaMonkey version 3.x is unknown.

[[Category:Scripting|{{PAGENAME}}]]
[[Category:Automation objects|{{PAGENAME}}]]
[[Category:CoClass SDBSongData|{{PAGENAME}}]]
[[Category:Interface ISDBSongData|{{PAGENAME}}]]

ISDBSongData::MusicComposer

2007-10-10T06:47:40Z

Imd1b4u: /* Property description */ Added warning that it is nonfunctional

{{MethodDeclaration|SDBSongData|ISDBSongData|Property Get/Let MusicComposer As String}}

===Property description===

Warning: This property is redundant and does not appear to be implemented properly under MediaMonkey version 2.5. Although it may be possible to set this property to some value, based on limited testing, the [[ISDBSongData::UpdateDB]] and [[ISDBSongData::WriteTags]] methods appear to ignore this property. Instead, any value in the [[ISDBSongData::Author]] property is saved where one would expect the value for this property to be saved. Furthermore, this property does not seem to display any values from the database or music files. Apparently, [[ISDBSongData::Author]] should always be used instead of this property.

The behavior of MusicComposer under MediaMonkey version 3.x is unknown.

[[Category:Scripting|{{PAGENAME}}]]
[[Category:Automation objects|{{PAGENAME}}]]
[[Category:CoClass SDBSongData|{{PAGENAME}}]]
[[Category:Interface ISDBSongData|{{PAGENAME}}]]

Scripting Tips & Tricks (MM4)

2007-10-07T04:25:10Z

Imd1b4u: Added link to Iviewer.dll (required by OLEView)

==(MediaMonkey) Scripting in general==

Using the SongData object, you can either update the database/library (UpdateDB) and/or update the file's tags (WriteTags). So there's no way to let the song changes be saved like the user selected in the Options panel (menu Tools > Options > Library > Tags & Playlists > "Update tags when editing properties").
However, the UpdateAll method for the SongList object ''does'' take into account this user-specified option. So you can create a new SongList object using SDB.NewSongList and add your SDBSongData object(s) to it. Then call the UpdateAll method on the songlist, and your song(s) will be saved in user-specified way.

MS Visual Studio contains a tool called [http://www.microsoft.com/downloads/details.aspx?familyid=5233B70D-D9B2-4CB5-AEB6-45664BE858B6&displaylang=en OLEView] ("OLE Viewer" or "OLE/COM Object Viewer") ([http://download.microsoft.com/download/win2000platform/oleview/1.00.0.1/nt5/en-us/oleview_setup.exe direct link]), which can show the type library of the SongsDB object: "MediaMonkey Library". It requires the Iviewers.dll, which is not included, but can be downloaded from [http://www.dlldll.com/downdll/2757.html here] or other 3rd-party locations. There, you can see all supported properties and methods of the MediaMonkey scripting interface. This can be handy to find out new scripting methods while the scripting help isn't up-to-date yet.
<br>The way to get there: ''OleView'' > Type Libraries > MediaMonkey Library > (double click)
<br>and then in the ''ITypeLib Viewer'' > SongsDB (MediaMonkey Library) > Interfaces.

When you un(dock) a dockable panel, the OnResize event is triggered twice:
*Once while the panel is being (un)docked with DockedTo = 0
*Once after the panel has been (undocked): with DockedTo = -1 (panel undocked) or DockedTo = X (panel docked, X is the number that represents the docking position)

A dockable panel always has to be added to the SDB.Objects dictionary. If you don't add it, it will be gone immediately after you created it.

There are still 2 scripting mechanisms available:
*Using the (mostly deprecated) ''old event mechanism'' (using ''Control''.OnClickFunc and ''Control''.UseScript), your global variables aren't remembered in the event handlers (e.g. kind of like the script is reopened). For those scripts, you had to use ''ParentControl''.ChildControl("control name") or save object references to SDB's ''Objects'' dictionary.
*Using the ''new event mechanism'', your global variables ''are'' remembered so you can use their values in the event handlers. The Objects dictionary is now only necessary to communicate/store object references between different scripts.
==> So always use the new event mechanism where you can. Only for option panels (sheets) this is not yet possible. There you'll need to store values between the main program and the event handlers in SDB.Objects, in the INI or in the Registry.

Changing the selected node from a script (using SDB.MainTree.CurrentNode = ...........) takes some time to happen, and it happens asynchronicly (the code execution doesn't wait until the node is really selected). For that reason, you can't use (get value of) SDB.MainTree.CurrentNode directly after you have assigned a new node to it (set value to), because changes won't have happened yet.

There are at least three ways to interact with MediaMonkey from an external program:
*Open the MediaMonkey.exe program with command line options (arguments).
*Using the same Windows Messages (SendMessage/PostMessage) as in Winamp (WM_USER and WM_COMMAND). MM partially emulates how WinAmp works (not 100%, but very close) and so it can use WinAmp plug-ins. The class name to communicate with is "Winamp v1.x".
*Using OLE Automation, which can be very easily used e.g. from VB Script.
*:<source lang="vb">Dim SDB : Set SDB = CreateObject("SongsDB.SDBApplication")</source>
*:<source lang="csharp">SongsDB.SDBApplicationClass SDB = new SongsDB.SDBApplicationClass();</source>
*:Be sure to set ''SDB.ShutdownAfterDisconnect'' to ''False'' if you opened the MediaMonkey program by calling the SDB object, and you don't want it to be closed when your external program exits (or if you disconnect the SDB object = COM link).

'''Helpful sites:'''
*http://www.microsoft.com/scripting

'''Handy editors:'''
*[http://www.vbsedit.com/ VBSEdit]
*[http://notepad-plus.sourceforge.net/ NotePad++]
*[http://www.pspad.com/ PSPad]
*[http://www.sapien.com/ PrimalScript]
*[http://www.microsoft.com/downloads/details.aspx?familyid=2f465be0-94fd-4569-b3c4-dffdf19ccd99&displaylang=en Microsoft VBScript 5.6 Debugger for Win 2000/XP]
*[http://www.editpadpro.com/ EditPad (Pro)]

==Visual Basic Script==

Usually indexes start from '''0''' (e.g. for normal arrays). However, sometimes (e.g. for string positions) they start from '''1'''.

'''Helpful sites:'''
*[http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/0a8270d7-7d8f-4368-b2a7-065acb52fc54.asp User guide and language reference]
*[http://www.microsoft.com/technet/scriptcenter/scripts/default.mspx?mfr=true Script Center Repository]
*[http://www.w3schools.com/vbscript/default.asp W3Schools VBScript]

==Database transactions==

Starting from MM 3.0 transactions are often used when working with database. It can cause some problems to script authors in case they don't know some details. One example where you can face a problem is when you use [[ISDBSongData::UpdateDB]] method while you have some SQL query open. What happens in this case is, that MM wants to start a transaction, but there's still an SQL query open. This results either in an error message (in debug build) or possibly an apparent freeze of MM in the release build.

In order to prevent this problem, you can either:
* Put all these DB operations in an transaction, i.e. use [[ISDBDatabase::BeginTransaction]] and [[ISDBDatabase::Commit]].
* Close already running SQL queries before you call things like [[ISDBSongData::UpdateDB]].

==SQL==

To easily create complex SQL queries, you can use the Query graphical user interface in Access interface, and show the SQL code when you are done.

One of the problems with SQL is that dates are often confused, which sometimes give programming bugs. The best way to circumvent this problem is by using the format #yyyy-mm-dd# for all dates in SQL (e.g. #2006-10-31# for 31th October 2006).

'''Helpful sites:'''
*[http://www.w3schools.com/sql/default.asp W3Schools SQL]

ISDBUIButton::UseScript

2007-10-07T01:58:28Z

Imd1b4u: Supplanted by ISDBScriptControl::RegisterEvent

{{MethodDeclaration|SDBUIButton|ISDBUIButton|Property Get/Let UseScript As String}}

===Property description===

Filename of a script where event functions are located.

===Comments===

This property has been supplanted by the [[ISDBScriptControl::RegisterEvent]] method.

[[Category:Scripting|{{PAGENAME}}]]
[[Category:Automation objects|{{PAGENAME}}]]
[[Category:CoClass SDBUIButton|{{PAGENAME}}]]
[[Category:Interface ISDBUIButton|{{PAGENAME}}]]

ISDBMenuItem::OnClickFunc

2007-10-07T01:57:37Z

Imd1b4u: Supplanted by ISDBScriptControl::RegisterEvent

{{MethodDeclaration|SDBMenuItem|ISDBMenuItem|Property Get/Let OnClickFunc As String}}

===Property description===

Name of the function that is called when the item is clicked. The function is expected to be in 'UseScript' file. There is one parameter passed to the function - this menu item ([[SDBMenuItem]] object).

===Comments===

This property has been supplanted by the [[ISDBScriptControl::RegisterEvent]] method.

===Example code===
<source lang="vb">
'The function to be called can look like:

Sub OnMenuItemClick( Item)
' Some code here
End Sub
</source>

[[Category:Scripting|{{PAGENAME}}]]
[[Category:Automation objects|{{PAGENAME}}]]
[[Category:CoClass SDBMenuItem|{{PAGENAME}}]]
[[Category:Interface ISDBMenuItem|{{PAGENAME}}]]

ISDBUIButton::OnClickFunc

2007-10-07T01:57:11Z

Imd1b4u: Supplanted by ISDBScriptControl::RegisterEvent

{{MethodDeclaration|SDBUIButton|ISDBUIButton|Property Get/Let OnClickFunc As String}}

===Property description===

Name of the function that is called when the button is clicked. The function is expected to be in [[ISDBUIButton::UseScript]] file. There is one parameter passed to the function - this button ([[SDBUIButton]] object).

===Comments===

This property has been supplanted by the [[ISDBScriptControl::RegisterEvent]] method.

===Example code===
<source lang="vb">
'The function to be called can look like:

Sub OnbuttonClick( Btn)
' Some code here
End Sub
</source>

[[Category:Scripting|{{PAGENAME}}]]
[[Category:Automation objects|{{PAGENAME}}]]
[[Category:CoClass SDBUIButton|{{PAGENAME}}]]
[[Category:Interface ISDBUIButton|{{PAGENAME}}]]

Scripting Tips & Tricks (MM4)

2007-10-06T17:19:00Z

Imd1b4u: Removed DebugView and WSHHelper. ~~~~

==(MediaMonkey) Scripting in general==

Using the SongData object, you can either update the database/library (UpdateDB) and/or update the file's tags (WriteTags). So there's no way to let the song changes be saved like the user selected in the Options panel (menu Tools > Options > Library > Tags & Playlists > "Update tags when editing properties").
However, the UpdateAll method for the SongList object ''does'' take into account this user-specified option. So you can create a new SongList object using SDB.NewSongList and add your SDBSongData object(s) to it. Then call the UpdateAll method on the songlist, and your song(s) will be saved in user-specified way.

MS Visual Studio contains a tool called [http://www.microsoft.com/downloads/details.aspx?familyid=5233B70D-D9B2-4CB5-AEB6-45664BE858B6&displaylang=en OLEView] ("OLE Viewer" or "OLE/COM Object Viewer") ([http://download.microsoft.com/download/win2000platform/oleview/1.00.0.1/nt5/en-us/oleview_setup.exe direct link]), which can show the type library of the SongsDB object: "MediaMonkey Library". There, you can see all supported properties and methods of the MediaMonkey scripting interface. This can be handy to find out new scripting methods while the scripting help isn't up-to-date yet.
<br>The way to get there: ''OleView'' > Type Libraries > MediaMonkey Library > (double click)
<br>and then in the ''ITypeLib Viewer'' > SongsDB (MediaMonkey Library) > Interfaces.

When you un(dock) a dockable panel, the OnResize event is triggered twice:
*Once while the panel is being (un)docked with DockedTo = 0
*Once after the panel has been (undocked): with DockedTo = -1 (panel undocked) or DockedTo = X (panel docked, X is the number that represents the docking position)

A dockable panel always has to be added to the SDB.Objects dictionary. If you don't add it, it will be gone immediately after you created it.

There are still 2 scripting mechanisms available:
*Using the (mostly deprecated) ''old event mechanism'' (using ''Control''.OnClickFunc and ''Control''.UseScript), your global variables aren't remembered in the event handlers (e.g. kind of like the script is reopened). For those scripts, you had to use ''ParentControl''.ChildControl("control name") or save object references to SDB's ''Objects'' dictionary.
*Using the ''new event mechanism'', your global variables ''are'' remembered so you can use their values in the event handlers. The Objects dictionary is now only necessary to communicate/store object references between different scripts.
==> So always use the new event mechanism where you can. Only for option panels (sheets) this is not yet possible. There you'll need to store values between the main program and the event handlers in SDB.Objects, in the INI or in the Registry.

Changing the selected node from a script (using SDB.MainTree.CurrentNode = ...........) takes some time to happen, and it happens asynchronicly (the code execution doesn't wait until the node is really selected). For that reason, you can't use (get value of) SDB.MainTree.CurrentNode directly after you have assigned a new node to it (set value to), because changes won't have happened yet.

There are at least three ways to interact with MediaMonkey from an external program:
*Open the MediaMonkey.exe program with command line options (arguments).
*Using the same Windows Messages (SendMessage/PostMessage) as in Winamp (WM_USER and WM_COMMAND). MM partially emulates how WinAmp works (not 100%, but very close) and so it can use WinAmp plug-ins. The class name to communicate with is "Winamp v1.x".
*Using OLE Automation, which can be very easily used e.g. from VB Script.
*:<source lang="vb">Dim SDB : Set SDB = CreateObject("SongsDB.SDBApplication")</source>
*:<source lang="csharp">SongsDB.SDBApplicationClass SDB = new SongsDB.SDBApplicationClass();</source>
*:Be sure to set ''SDB.ShutdownAfterDisconnect'' to ''False'' if you opened the MediaMonkey program by calling the SDB object, and you don't want it to be closed when your external program exits (or if you disconnect the SDB object = COM link).

'''Helpful sites:'''
*http://www.microsoft.com/scripting

'''Handy editors:'''
*[http://www.vbsedit.com/ VBSEdit]
*[http://notepad-plus.sourceforge.net/ NotePad++]
*[http://www.pspad.com/ PSPad]
*[http://www.sapien.com/ PrimalScript]
*[http://www.microsoft.com/downloads/details.aspx?familyid=2f465be0-94fd-4569-b3c4-dffdf19ccd99&displaylang=en Microsoft VBScript 5.6 Debugger for Win 2000/XP]
*[http://www.editpadpro.com/ EditPad (Pro)]

==Visual Basic Script==

Usually indexes start from '''0''' (e.g. for normal arrays). However, sometimes (e.g. for string positions) they start from '''1'''.

'''Helpful sites:'''
*[http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/0a8270d7-7d8f-4368-b2a7-065acb52fc54.asp User guide and language reference]
*[http://www.microsoft.com/technet/scriptcenter/scripts/default.mspx?mfr=true Script Center Repository]
*[http://www.w3schools.com/vbscript/default.asp W3Schools VBScript]

==Database transactions==

Starting from MM 3.0 transactions are often used when working with database. It can cause some problems to script authors in case they don't know some details. One example where you can face a problem is when you use [[ISDBSongData::UpdateDB]] method while you have some SQL query open. What happens in this case is, that MM wants to start a transaction, but there's still an SQL query open. This results either in an error message (in debug build) or possibly an apparent freeze of MM in the release build.

In order to prevent this problem, you can either:
* Put all these DB operations in an transaction, i.e. use [[ISDBDatabase::BeginTransaction]] and [[ISDBDatabase::Commit]].
* Close already running SQL queries before you call things like [[ISDBSongData::UpdateDB]].

==SQL==

To easily create complex SQL queries, you can use the Query graphical user interface in Access interface, and show the SQL code when you are done.

One of the problems with SQL is that dates are often confused, which sometimes give programming bugs. The best way to circumvent this problem is by using the format #yyyy-mm-dd# for all dates in SQL (e.g. #2006-10-31# for 31th October 2006).

'''Helpful sites:'''
*[http://www.w3schools.com/sql/default.asp W3Schools SQL]