Free JUKEBOX to those who can help me!

GKite

Registered User.
Local time
Today, 22:09
Joined
Mar 22, 2002
Messages
29
OK just so there's no confusion this jukebox i'm referring to will be an access database, not real hardware.

My project: I own almost 800 CD's. I'm writing a database, that will have these CD's embedded into the tables. Once the music is placed into the database, there will be a type of 'jukebox' interface at which you can sort for music, create 'favorite' compilations, and of course play them. I've come a long ways, and right now I'm at the point where I need to copy the selected songs back to the C drive, so they can be played back using winAMP, or be ready for CD-Burn.

Anyhow, I don't understand how to export an OLE object(songs) to the C drive. Additionally, I have to write a text file that winAMP can use as a play list. I should be able to figure this one out, but any help would be appreciated. Mainly, the OLE save part is giving me a big headache.

Anyone who can give me useful information to complete these remaining tasks will be given a copy of the final product. It will not include the actual data(music) as the file will be about 50Gigs and music sharing is illegal. It will definitely be a cool program for personal use though!
 
GKite

With OLE obeject, you can right click on the picture in access, then choose 'copy'.
Open Windows Explorer and simply 'paste' the object into a file.

Hope that helps.
Tom

[This message has been edited by wizcow (edited 03-24-2002).]
 
I can't really helpful because what you're doing is way too advanced for me. Does this post qualify for a free copy of your database?? Its sounds brilliant! I wanna try it out!
 
wizcow- unfortunately I need to automate the exporting process. The user might want make a playlist dozens of songs long.

NeilW- no that doesn't count! But with you're enthusiasm i'll add you to my list
wink.gif


NEW info - apparently access databases have a limit of 2 gigabytes, so I'll have to change the gameplan a little. But I still need a way of automating exportation of embedded files.
 
GKite - when I've wanted to embed a file in access what I have done is NOT store the file itself inside the DB, instead I've stored a link field in the form of the filepath to the file in question, then when I've needed to retrieve(open) the file, I've just hyperlinked to the appropriate file.

I understand you are dealing with sound files but I think the same approach may get you round your 2Gb limit.

Remember that this is only a 2Gb limit PER DATABASE, therefore if you have one front end linked to 10 backends you literally have access to 20Gb of data, now whether you PC can handle it is another matter entirely.

Does this qualify as help
wink.gif
 
Yes that qualifies as help!

New question: I'm trying to make a button that will run an application. The button wizard isn't working as I get an 'invalid call or procedure' error. Anyone know the vba for a simple 1 line way of opening or running an application? Hyperlinking is not an as the app. in question will have varying names.
 
Do you mean
Shell("Path to your Prog.exe")

Is that helpfull aswell
smile.gif


HTH
John
 
Can you be more specific? I've tried both of these ways and niether is working for me. Any ideas?

Shell (strSong)
Shell ("c:\softjuke\files\28.mp3")
 
have you tried:

Application.FollowHyperlink strSong

Let the host computer decide which application to open the file in as any normal hyperlink would using the natural file associations.
 
You need to run to the exe for the app you want to run.

Try the following assuming you're using the windows standard cd player or modify accordingly.

Shell ("Shell ("C:\WINDOWS\CDPLAYER.EXE c:\softjuke\files\28.mp3")

HTH
John
 
Both good options. I think I will use the non-hyperlink option just to avoid any additional pop ups like "are you sure you want to open... may contain virus...".

Of course the downside is the player location, but the player will be included and just has to be installed at the default method.

2 more peeps on my list
wink.gif
 
You could always set the path to the player as a field in a table and call it with a dim statement, then people could imput their own path and maybe even their own player software e.g.

Dim strPlayer as string
Dim strSong as string

Set strPlayer = DLookup("PlayerPath","TableName")
Set strSong = DLookup("SongName","SongTable","SongID = Forms!YourForm!SongID")

Shell(strPlayer strsong)

Thus the player could be installed in any location. The form where you set the player location would have only one record and by setting it not to allow additions you would never get more than one record in the table. Just remember to put one record in to start with!!!
 
GKite your a great bloke/woman! Thanks a lot, I'll really appreciate that. If there's ever anything I can do to help you then i certainly wont hesistate.
 
NielW- If you wanta copy you need to have your email address available!!! update you're profile!!!
 
Looks like you've gotten the help you needed, but I sure wouldn't mind seeing a copy of your database
smile.gif
 

Users who are viewing this thread

Back
Top Bottom