Hello. Please, help me. I have created a monster. What started as just
something to help me keep track of our clients, because I have such a
poor memory, has turned into an indispensable monster. I have nearly
3000 clients in it now, and use it for keeping track of conversations,
emails address and contact info, and all sorts of stuff.

I have a memo field where I put information on the details of the
music production we are working on for them. After a while it becomes
more and more bogged down as time passes and we do fresh songs for
them, sifting back through this very useful memo field. So, I want to
make a fresh table for the song itself. I have a tabbed form I have
room for another tab on, which I want to import information from the
song production table. Can someone give me a rough clue about how to
link these two tables. All the help files assume you somehow already
know how to do that, or I can't find such infomation. I have a primary
key in the main table that identifies each unique client. I can make
tables from scratch, so at least I'm that far along. I got as far in
the help file as realizing I will need a one to many sort of
relationship but then it starts assuming I have a reasonable amount of
intelligence or training, which I do not.

My boss sort of caught me using this database instead of the old
rolodex and hardcopy files and I can find information in a flash, and
he gleefully commanded me to come up with a similar way of tracking
and quantifying their song productions. I am a virtual slave and have
no helpers, or budget so I appreciate please don't suggest I hire a
professional programmer, I would love to do that but it's not an
option.

Just ...need ...a little ...help. Thanks and I can be more specific on
details if that will help.

TIA


steve

Steve:

If I understand your situation you have 2 tables.
One with a primary key and Name, Addr, etc.
The other with a link to the primary Key and a memo field relating to
songs.

There are two ways to link the tables.
One is to use a query. Assume the Primary key in the first table is
named PID and that each record in the song table has a field called
MID (master ID) which relates to the PID in the first table.
You creqte a query with both tables, highlight the PID field and drag
it to the MID field. You have created the relationship.
You can base a form on the query.

I mention this because you need to know it, but it isn't what you
really want to do.

Nor do you want to use a tab in the form.

You want a subform based on the song table.

When you create a subform control you will be asked how to link the
subform and the main form. You link PID to MID.

Now you will have a form that has a master record and a subform that
lets you brwos through the songs.

Good luck

Ira Solomon

If I understand you
On Fri, 08 Oct 2004 03:50:57 GMT, Damon LePleur <nunthee (AT) gak (DOT) net>
wrote:

You understood me and after long head scratching, you're right it was
simple to link them with the relationships tool, and then base the
form and reports on a query that combined the information. I learned I
think, far more than I wanted to know. I think one problem is that it
was so simple that no one who knows Access could probably imagine any
one not knowing that. The subform is now based on a query and I can
use any table or make new ones and throw the fields in there left and
right. It's a kick!

That's in hindsight of course.

I appreciate your response very much and it all seems to be working
now, and I have grandiose plans that even my boss cannot yet
foresee... heh heh.

steve

On Sat, 09 Oct 2004 18:24:11 -0400, Ira Solomon
<isolomon (AT) solomonltd (DOT) com> wrote:

Access tends to suck people in.
Microsoft markets it as a simple, entry level system. But once you
get started you find out that there are things you want to do that are
not simple.
This is a common problem with Access.

Good luck.
Ira Solomon

On Mon, 11 Oct 2004 23:34:47 GMT, Damon LePleur <nunthee (AT) gak (DOT) net>
wrote: