gram

I agree. I've gave up on him. Yep. Me too. Got the attributes if you ignore the fact that he never uses his head.

Perhaps they could get rid of LAX and that would cut down on emissions too? Or get rid of the 101 highway and get people cycling to Santa Barbara? There are far too many bloody cars/SUVs and Winnebagos on that road from LA to San Franscisco anyway so surely the answer is getting rid of it? Only in America.

fuck me its along time since I thought about the redskins. I used to be in a five a side team with the drummer I am off to find "keep on keeping on" saw them a load of times. was at the tube when they played.billy Bragg was on too. Love Keep on Keepin on there are vids of them on youtube!

freak scene - dinosaur junior i just saw a face i cant forget - the beatles janey jones - the clash this charming man - the smiths owt by the redskins plenty more too but cant think

owt by the redskins

Mates dad had psycholgical problems - he was a paranoid schizophrenic and as kids (about 16 ish ) we used to move his garden gnomes a few inches close to his front door every night. We lived in same street. He freaked out and ran down the street shouting 'uncle Peter' repeatedly eventually.Still not sure why he shouted that. Our mate was livid and to this day still doesnt know it was us. Guilt

Rifles and Tom Russell (who is a country and western Billy Bragg)

Ozomatli

It sounds like what you're doing is correct, sounds like two tables... Table 1 - CD ID CD Title Artist Year etc Table 2 - Tracks ID CD_ID Track Name Running Time etc In both cases make the ID fields the Unique Primary Key. Link the two together via a One to Many on the ID and CD_ID field and it should work, if you look at the SQL view of the Query it should look summit like this: SELECT * FROM Tracks INNER JOIN CD WHERE cd.ID = Tracks.CD_ID; What exactly is happening? nothing at all? or are you getting an error message? 194303[/snapback] I have named the "CD_ID" field "Track Number" and have also inserted a field called "Album Title". Which of these should I link the ID from table 1 to .... and how do I link it to 2 fields in the 2nd table, it won't let me do it ??? Table 1 has ID, Title, Artist, Year, Format, Comments Table 2 has ID, Album Title, Track Nr, Song title, comments 194898[/snapback] basically you need to do the following: Table one Id as primary key and title, artist, album Table 2 Id (no primary key in this table), tracks (but if e.g. The Clash is 1 in table 1, then you need to label every track on this album 1 in the id field in this table) I would put track number, year, etc in this table Relate the two id fields from table 1 to table 2. that works. There is an easier way but its late and brain isnt working. Try it though. It will work.

It sounds like what you're doing is correct, sounds like two tables... Table 1 - CD ID CD Title Artist Year etc Table 2 - Tracks ID CD_ID Track Name Running Time etc In both cases make the ID fields the Unique Primary Key. Link the two together via a One to Many on the ID and CD_ID field and it should work, if you look at the SQL view of the Query it should look summit like this: SELECT * FROM Tracks INNER JOIN CD WHERE cd.ID = Tracks.CD_ID; What exactly is happening? nothing at all? or are you getting an error message? 194303[/snapback] I have realised I am running '97, and have upgraded it to office 2000 to see if it works better [ i thought i put 2000 on when I got the PC but obviously not] ...I have been told it will do so I will try again later mate and let you know. What was happening was simply that I was not getting the + sign , and that is the format I wanted to do it in as it is the way I am learning to do it. I realise I can do it via reports/queries but I'm not quite at that stage yet .... the annoying thing is all the reports/queries section of access quite easy, it is the relationship and subdata sheets that is a bit difficult to grasp or should I say I did get it right and thought it was wrong because the old version wasn't doing what the up to date ones do. The only messages I am getting is validation ones, sometimes. I have been told to use a double primary key to get a "one to many" relationship but it won't let me do this either. Your table 1 above is exactly what I have for table 1, and in table 2 I have got Album title [again - to connect a relationship] along with Track number, track title and a section for comments etc. 194802[/snapback] Didnt realise you were going to put the songs on it leazes. To be honest I would probably just decice to use something like itunes and burn your cds onto it. That way gracenote creates what you want - i.e. gives you names of albums and song lists as well as keeping a copy of cd on pc. doesnt take up much memory relative to an average pcs storage capacity. Also means you dont have to type anything in.If you do persevere with the database then feel free to email the idea to me and i will create it for you. wont take long. depends on what you want doing. If its just a basic one ot many relationship then create the table as pud says then go to relationship and link from table one ot two. But be very careful with the option for referential integrity. This is particularly important when you dont use the autofields and depends on you to enter accurate data. Cheers

Not sure what youre trying to do but a flat file table would be enough for this type of database - linked to a basic query. You could do that and link it to a report. You trying to build a system for them? If that is the case then I would do a web based one using something like mysql or just a dreamweaver thing linked to your access flat file. Alternatively, I have thousands of cds and just put them in alphabetical order.