![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, I'm not very experienced with filemaker and I need to design the following: I'm creating a "cd database" which will include fields like: Artist: Name of the cd: Year of release: And besides, I need to create a list of the tracks contained in the same album, each one with a unique number. How can I achieve this? How can I create these subfields? (one for the track and one for the unique number?) Thanks in advance, Daniel estudi (AT) rosazul (DOT) com |
#3
| |||
| |||
|
|
I'm creating a "cd database" which will include fields like |
#4
| |||
| |||
|
|
musicdld (AT) yahoo (DOT) es wrote: Hello, I'm not very experienced with filemaker and I need to design the following: I'm creating a "cd database" which will include fields like: Artist: Name of the cd: Year of release: And besides, I need to create a list of the tracks contained in the same album, each one with a unique number. How can I achieve this? How can I create these subfields? (one for the track and one for the unique number?) Thanks in advance, Daniel estudi (AT) rosazul (DOT) com You create a TABLE for each set of information you want to hold, with appropriate fields. CDS, for instance, would have Title, Artist, ReleaseYear, and anything else, like maybe the catalog number, perhaps a container field for the cover art. A unique ID or MATCH field is also necessary. It should be something that will be automatically generated by the system, something that cannot be changed once it is created (see the Auto-Enter tab under Options in the Field Definitions). Your CUTS table would have CutNumber, CutTitle, and an ID field. In the Relationships Graph in Define Database, connect the two tables by dragging ID from one to meet ID from the other. Make sure that you specify the relationship so that new records can be added to CUTS through the relationship. On the layout for CDS, you already have the fields in that table. Add a portal to the layout. The only relationship you have is to CUTS, so that should be self evident. You'll be asked what fields you what to appear (the ID doesn't have to show). Now create a new record in the CDS table, populating the fields appropriately. Click in the portal, and you'll be able to add the cuts. This is a somewhat simplified description of how to create a relational database, but you have to start somewhere. It might help you to have something to pick apart to see how it's put together. I have a working model (FM7) of what you're trying to do if you want to look at it. Nothing fancy (I'm still developing), but it does the job. Matt |
#5
| |||
| |||
|
|
Hi, I'm creating a "cd database" which will include fields like It is very easy to do using our product WinCatalog Standard. You may read about it here: http://www.wincatalog.com It will retrieve all info about Audio CDs from the Internet (http://freedb.org) Besides of cataloging Audio CD, you will be able to catalog your MP3s, documents and regular files. After cataloging you will be able to export your collection into HTML or CSV for publishing or further editing. We have Christmas prices now (20% discount until December 31, 2005). Have a nice day! -- Michael. |
#6
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |