Prev: splitting database
Next: Importing Tab Delimited Text File to an Existing Table in Access
From: Dorian on 3 Feb 2010 15:36
FK is foreign key'and PK is primary key. You need to understand what these 2
extremely important concepts are. I suggest googling them.
Basically, a PK is a column (or columns) in a table that uniquely identifies
a row. A Fk is a reference to a PK from a related table.
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".


"SandraRae2000" wrote:

> I'm trying these things you suggested, but what is FK?
>
> "Fred" wrote:
>
> > Do what Jeff said.
> >
> > Adding / reinforcing the fine points, start by pushing your Access book and
> > the computer aside and decide on what the ENTITIES that you want to database
> > are, and what the relationships are between them. You might even discuss
> > that further here in this forum at this early important stage.
> >
> > My first guess is that main main entity is dtatsets, which are instances of
> > receiving data, or, more specifically, instances of data being recorded or
> > summarized by your sources.
> >
> > "Sources" will probably be another major table. If so, a good guess would
> > be to put a SourceID autonumber PK field in your Sources table, and an
> > integer "SourceID" FK field in your Datasets table and link those two fields.
> >
> > "Hazards" will probably be more of a "lookup table" to fill a "hazard" field
> > in your Datasets table.
> >
> > Good luck!
> >
> >
> >
From: Fred on 3 Feb 2010 16:15
BTW that was just my first guess, not knowing the details of your
business/agency. But a good place to start, even if imperfect.
FK = Foreign Key

To answer this and your linking question.

Let's say that you just entered a new Source, the city of Las Vegas, NV.
You have an autonumber PK field named SourceID. When you entered that
record, Access automatically gave it a source ID number of 1234.

Now you have your first two datasets: December 2009 Plutonium leaks, and
January 2010 Plutonium leaks. You want to enter these and record where they
came from via a link. There are three steps to linking:

One time: Put an integer (not autonumber) field called
"IDNUmberofSourceofThisDataset" (or "SourceID" as I said before is also OK)
into your Dataset table. This defines the intended use of this field as a
"Foreign Key" ....FK is a USE, not a structure setting in Access like PK.

One time: Open the relationships window and draw a line between this field
and the "SourceID" field in your source table.

When adding those two DataSet Record, write "1234" in your
"IDNUmberofSourceofThisDataset" field.

Later this loading of the field and and use of the links gets automated by
forms.

From: Steve on 3 Feb 2010 16:54
If the responses you have gotten are all greek to you, I would like to offer
tp build the database for you. I provide help with Access, Excel and Word
applications for a small fee. My fee to help you would be very reasonable.
Contact me and let's discuss how we can work together to create your
database.

Steve
santus(a)penn.com


"SandraRae2000" <SandraRae2000(a)discussions.microsoft.com> wrote in message
news:819D76E2-93D9-42BC-AB20-387A063FE431(a)microsoft.com...
> Rookie user: Access 2007, Using "Picture Yourself Learning: Microsoft
> Access
> 2007" as reference guide.
> Need suggestions for how to structure what seems to me to be a very
> complicated DB. I want to build it the best way the first time, so I don't
> do
> a lot of work and not have it do what I need.
> Here's what I need to do:
> Track GIS datasets for about 50 natural and environmental hazards.
> The data itself does not need to be tracked. I do need to track its source
> (National, State, County or City data) and know its date of creation, and
> frequency of updates for example.
> I don't know whether to create one Table with tons of fields, and then try
> to figure out queries. Or should I create tables for each specific hazard
> like Earthquake, Flood, etc.? Should I create tables for each source of
> data
> such as National, State, County and each City from which I obtain data?
> What I want to be able to do is easily determine which updates to which
> data
> need to happen when, which data came from which source, what data is
> available for each specific hazard and what datasets overlap at the
> National,
> State, County and City levels.
>
> Here's an example: I have data from the National Wetlands Inventory that
> is
> updated annually.
> I also have data from the County that is updated quarterly. The State and
> the Cities have no additional data. I need to be able to know, for 50
> different hazards or issues, the source of the data, how often it's
> updated,
> a scheduled reminder when it's time to update if possible, and a field
> with
> a hyperlink to the actual data or metadata.
>
> My reference book includes instructions on Creating a DB, Creating and
> Editing Tables, Improving Table Design and Creating Relationships,
> Creating
> Forms, Creating Simple Queries, Creating Queries that filter and Summarize
> Data and Creating Reports. I think it's a beginner type book - well it
> must
> be, if I'm able to sort of understand it. But I'm hoping someone who
> understands the whole picture can tell me what parts to build and where. I
> can follow directions, but can't see the forest for the trees at this
> point.
>
> Any help would be extremely appreciated, and paid forward!
>


From: StopThisAdvertising on 3 Feb 2010 17:52

"Steve" <notmyemail(a)address.com> schreef in bericht news:uogrBuRpKHA.4348(a)TK2MSFTNGP06.phx.gbl...
> If the responses you have gotten are all greek to you, I would like to offer tp build the database for you. I provide help with
> Access, Excel and Word applications for a small fee. My fee to help you would be very reasonable. Contact me and let's discuss how
> we can work together to create your database.
>
> Steve
> santus(a)penn.com


From now on I am going to hunt each and every post of you Steve
Again.... It won't work but that 's no problem... it's a shame...
--
Get lost $teve. Go away... far away....

Again... Get lost $teve. Go away... far away....
No-one wants you here... no-one needs you here...

This newsgroup is meant for FREE help..
No-one wants you here... no-one needs you here...
OP look at http://home.tiscali.nl/arracom/whoissteve.html
(Website has been updated and has a new 'look'... we have passed 11.000 pageloads... it's a shame !!)

Arno R


From: John... Visio MVP on 3 Feb 2010 18:41
"Steve" <notmyemail(a)address.com> wrote in message
news:uogrBuRpKHA.4348(a)TK2MSFTNGP06.phx.gbl...
> If the responses you have gotten are all greek to you, I would like to
> offer tp build the database for you. I provide help with Access, Excel and
> Word applications for a small fee. My fee to help you would be very
> reasonable. Contact me and let's discuss how we can work together to
> create your database.
>
> Steve
> santus(a)penn.com

Still pimping your questionable services?


Stevie is our own personal pet troll who is the only one who does not
understand the concept of FREE peer to peer support!

These newsgroups are provided by Microsoft for FREE peer to peer support.
There are many highly qualified individuals who gladly help for free. Stevie
is not one of them, but he is the only one who just does not get the idea of
"FREE" support. He offers questionable results at unreasonable prices. If he
was any good, the "thousands" of people he claims to have helped would be
flooding him with work, but there appears to be a continuous drought and he
needs to constantly grovel for work.

John... Visio MVP



First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: splitting database
Next: Importing Tab Delimited Text File to an Existing Table in Access