dbTalk Databases Forums  

related fields (CD database)

comp.databases.filemaker comp.databases.filemaker


Discuss related fields (CD database) in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
musicdld@yahoo.es
 
Posts: n/a

Default related fields (CD database) - 12-16-2005 , 05:39 AM






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>


Reply With Quote
  #2  
Old   
Matt Wills
 
Posts: n/a

Default Re: related fields (CD database) - 12-16-2005 , 06:55 AM






musicdld (AT) yahoo (DOT) es wrote:

Quote:
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



Reply With Quote
  #3  
Old   
Mar
 
Posts: n/a

Default Re: related fields (CD database) - 12-16-2005 , 11:01 AM



Hi,

Quote:
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.



Reply With Quote
  #4  
Old   
Bill
 
Posts: n/a

Default Re: related fields (CD database) - 12-16-2005 , 01:18 PM



In article <WOyof.3812$Y2.1891@trndny04>, "Matt Wills" <Im (AT) Witz (DOT) End>
wrote:

Quote:
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
I add the following:

In the CD table, we will call the ID field kpCDID. Make this an
automatically generated serial number that can not be edited. This will
be unique for each CD, and will be one side of the relationship to CUTS.

In the CUTS table make two ID fields. One we will call kpCUTSID, which
would be an automatically generate serial number that can not be edited.
Do this for possible future use.

The other, which we will call kfCDID, will simply be a number field. It
will be the CUTS end of the relationship to CD. It will be automatically
filled when a new CUTS record is created via the relationship from CD.

Bill Collins

--
For email, remove invalid.


Reply With Quote
  #5  
Old   
musicdld@yahoo.es
 
Posts: n/a

Default Re: related fields (CD database) - 12-19-2005 , 03:50 PM



Thanks for your help: I did it!
Daniel


Mar ha escrito:

Quote:
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.


Reply With Quote
  #6  
Old   
musicdld@yahoo.es
 
Posts: n/a

Default Scripting Relative numbers - 12-19-2005 , 03:57 PM



Hi I want to create a script that automatically writes relative numbers
(02, 03, 04) on a field (displayed on its portal setup) from a related
file. (as many relative nums. as num. of fields displayed).

thanks,

Daniel


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.