Forum Moderators: phranque

Message Too Old, No Replies

How the heck do this?

I cant get MS Access 2000 to do what i want!

         

eggy ricardo

5:20 pm on Jul 11, 2003 (gmt 0)

10+ Year Member



Hi webmasters! (& webmasteresses)

Now i know this ain't strictly webmastering but i thought you clever guys might be able to help me out.

I have MS Access 2000 and i am creating a database for a friend of mine who runs a mobile disco service so if he gets requests he can search to see if he has the song wanted.

So far i have created a table with all the tracks of all his CDs on and their artists. But now what i want is an album column. However what i would also like is a column to say wether he had them with him at the time or not. My original idea was to create another table with the name of each album and then a yes/no colum for if he has them with him or not.

Now is where i get stuck.

Is there a way to link the two so that i can select which alubum each track is for and then in the next colum it automatically tells him wether he has it with him or not. (Also auto updating as he will do a quick 'stock check' before every disco).

I have dabbled with the lookup wizzard tool but to no avail.

Can anyone help me out?

THANKS
eggy_ricardo

PS hope u understand. If theres owt i ain't made clear let me know. Thanks again!

Marketing Guy

5:37 pm on Jul 11, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Yeh, each table needs to have a record id.

(track table)track_id
(album table)album_id

On the track table you also add an album_id field.

Then create a relationship between the 2 album_id fields (er cant remember what type offhand, so just mess around until it works!).

One of the relationship options opens the album table within the track table when you are in data entry view.

So when you enter a new track - you expand the album table and enter the rest of the data (ie, adding a new album name will add a new album_id as it is the tables primary key - autonumber).

So you add the following:

Track_1 (TT), Album_name1 (AT) - album_id will be 1
Track_2 (TT), Album_name1 (AT) - album_id will be 1

Track_1 (TT), Album_name2 (AT) - album_id will be 2

And so forth (TT - track table, AT - album table).

Does this make sense? I dont think ive explained it very well.

Basically you use the relationships tool to link the common field, album_id, which is your primary key on the album table.

Scott

Marketing Guy

5:40 pm on Jul 11, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Oops forgot stuff! :)

1. Naturally the album table can have more fields, including the Yes/No field.

2. You can setup a query to do the quick check - just get it to filter all albums with the yes/no field = yes (or "checked").

Scott :)

eggy ricardo

8:53 am on Jul 13, 2003 (gmt 0)

10+ Year Member



Yeah thanks...

I think i understand.

I'll have a mess around sometime and hopefully I'll get it working

Thanks

eggy_ricardo