Prev: splitting database
Next: Importing Tab Delimited Text File to an Existing Table in Access
From: Keith Wilby on 4 Feb 2010 09:20
"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.
>

FWIW I have a "hazardous materials" tracking database which you're welcome
to a copy of if you like. It may be of no use to you whatsoever, but then
again it might just help. Drop me a line if you'd like to take a look.

Keith.
www.keithwilby.co.uk

From: Fred on 4 Feb 2010 11:18
Sandra,

See my response of today, hidden several posts back in the above thread.
From: SandraRae2000 on 4 Feb 2010 16:09
Thanks Fred!
I'm going to follow your instructions of how to approach this. Then, if that
fails, I'll consider your other suggestion. If I do go the professional
route, what is a typical fee structure like? While learning all of this and
starting from scratch is extremely fun and rewarding, I'm supposed to be
focusing on other aspects of my operation! But, I have more time than money!!
Thanks so much for your help and advice.
Sandra

"Fred" wrote:

> Hi Sandra,
>
> The confluence of two items (you are barely started on the big job of
> learning Access and are in a big hurry to get this up and running then you
> are probably going to need many hours of help from an expert.
>
> If I were looking for such help, expert help, I scan back through this
> discussion groupl for regular contributors who appear to be in the business
> and who aren't the one person (who you've now met) that abuses this group by
> hitting people up for money, and email a couple of them.
>
>
> - - -
>
> Alternatively, hit the books really hard and ask questions here. At the same
> time that you are reading the books, here is your overall process:
>
> 1. Shut the computer off and decide the real world entities are that you
> want to database. Use the discussion in this tread to guide you.
>
> 2. Design Tables and links between them to implement your decisions from#1
>
> 3. Make rudimentary queries to look at your individual tables. Not
> essential, but a good next step. And (although not essential) make single
> table queries which will be the middlemen (record sources) for your forms and
> reports.
>
> 4. For cases where you need to see & enter the data from multiple linked
> tables all at once, make a form with subform(s) to do so. For example, to
> see an organization that sends datasets, then the show and enter their data
> sets underneath them, make and "Organizaiton" form, and put a "Data set"
> subform underneath it.
>
> 5. Make rudimentary reports for single tables
>
> 6. In a similar manner an situaiton as number 4, make reports with
> subreports to show data.
>
From: Armen Stein on 4 Feb 2010 16:28
On Thu, 4 Feb 2010 05:47:02 -0800, Fred
<Fred(a)discussions.microsoft.com> wrote:

>Alternatively, hit the books really hard and ask questions here. At the same
>time that you are reading the books, here is your overall process:
>
>1. Shut the computer off and decide the real world entities are that you
>want to database.

This is really good advice. Every new database design should start
off as a pencil or whiteboard sketch of just the basic tables and how
they're related.

If you haven't already found it, a really good book for getting
started is Database Design for Mere Mortals by Michael Hernandez.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

From: Fred on 4 Feb 2010 17:15
I can't answer the fee structure question. I do this as a break from work
rather than to make money. Plus my area is data architecture and the
combination of databasing real world business processes. When it comes to
true Access developer stuff, you'll find me asking questions rather than
answering them.

If you're serious about getting more substantial help, I would do what I
recommended previously. Scan previous posts here for helpful people who
appear to be in the business, who haven't hit you up for money.



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