Your current table should arguably be re-designed, as you currently have duplication of data for the album field at least. However this isn't essential, as you are just using more size than you could.
In order to save playlists I would recommend 3 tables, one to save the User info, one to save Playlist info, and one to save the contents of the playlist. eg:
Users
UserID - Autonumber/Identity
UserName - String/Char/Varchar
Playlists
PlayListID - Autonumber/Identity
UserID - reference to the UserID of the 'owner' in Users
PlayListName - String/Char/Varchar
PlayListContents
PlayListContentsID - Autonumber/Identity
PlayListID - reference to the PlayListID in PlayList
SongID - reference to the ID in your current table
To find all playlists for a user, you can use SQL like this:
Code:
SELECT P.PlayListID, P.PlayListName
FROM Playlists P
INNER JOIN Users U ON (U.UserID = P.UserID)
WHERE UserName = '<user name here>'
To list the songs in a playlist, you can use SQL like this:
Code:
SELECT t.*
FROM Playlists P
INNER JOIN PlayListContents C ON (C.PlayListID = P.PlayListID)
INNER JOIN <CurrentTableName> t ON (t.ID = C.SongID)
WHERE P.PlayListID = <PlayListID from the SQL above>