Re: Let's start again
From: Bruce (anonymous_at_discussions.microsoft.com)
Date: 07/16/04
- Next message: fredg: "Re: concatenating text fields in a report"
- Previous message: Albert D. Kallal: "Re: From Access to Word"
- In reply to: Continental Translations: "Let's start again"
- Next in thread: Bullschmidt: "Re: Let's start again"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 16 Jul 2004 13:09:32 -0700
First thing is that you should keep one thread going,
otherwise it can be difficult to know what has happened in
the past.
Good question about using a new table or the Details
table. If each translator had one source and one target
language, or some definite maximum, I would say to put it
in the Contact Details table (tblContactDetails). Since
you could have somebody with lots of combinations, I would
say to use a new table.
Let's call your autonumber Primary Key (PK) from the
details table ContactID. Make a new table for languages
(tblLanguages), with LanguageID as the PK ContactID as the
foreign key (FK), and fields for Source and Target.
Establish a relationship between the two tables. Make a
form (use autoform to get started) from each table (call
them frmContactDetails and fsubLanguages), and set up
fsubLanguage as a subform on frmContactDetails. One way
to do this is to drag the icon for the languages form onto
the contacts form in design view. Check Help for more on
this.
Whether you add Specialty to the tblContactDetails table
or to another depends for one thing on whether the
specialty applies to all source and target languages. If
so, and if you want to limit it to three or so, you could
have that information in tblContactDetails table. If the
specialty varies for different source and target languages
(for example, Marketing specialty might not apply to all
language combinations for one translator), you could add
the information to the languages table, so that selecting
Source and Target would also mean selecting a Specialty
(or Specialties) relevant to that combination. Or you
could take a similar approach as with tblLanguages, and
link the Specialties table (tblSpecialty) to either
tblContacDetails in identical manner as with tblLanguages,
or link it to tblLanguages, using LanguageID as the FK in
tblSpecialty. It all depends on your needs. After
establishing the relationships, make a form out of
tblSpecialty and set it up as a subform to either
frmContactDetails or fsubLanguages.
I think this will get you started. I probably will not
check this newsgroup again until Monday. Good luck.
>-----Original Message-----
>OK, lets start from the beginning as I agree I am not
making much sense.
>
>What i'm after is a database do keep a list of all my
freelance translator
>and their contact details (name, address, telephone
number etc.....) All of
>my contact entries will be automatically given a Contact
ID (that being my
>primary key for this table) Now, for each freelance
translator, they will
>each have one or more language pairs, the first language
being the 'source'
>language and the second being the 'target' language which
they work between,
>ie French into Spanish and English into Spanish. So, for
example, my first
>contact, William Brown, will be able to translate between
French (source
>language) and German (target language), and English
(source language) and
>German (target language). Now, I am not too sure whether
I should put these
>language details in the 'Contact Details' table or in a
new table. I also
>want to be able to add a price per 1000 words that
each 'contact' charges.
>
>Eventually, what I want to be able to do, is search on a
few principles. For
>example, I want to be able to search via surname, source
language, target
>language, source language AND target language together
and price.
>
>Any help??
>
>
>
>
>
>.
>
- Next message: fredg: "Re: concatenating text fields in a report"
- Previous message: Albert D. Kallal: "Re: From Access to Word"
- In reply to: Continental Translations: "Let's start again"
- Next in thread: Bullschmidt: "Re: Let's start again"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
