Table design help

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

JEM - 28 Jun 2007 23:24 GMT

I have to create a database which monitors outcomes every four hours. I have
created a table which covers 1 day and have then copied this to make the 2nd
day and so on. The problem I have, this monitoring can last 1 day or it has
been known to last up to 6wks in some cases. Is there an easier way to do
this as the dates of when it starts and finishes are important.

Also for each outcome a yes or no has to be achieved, if a no has been input
I have made a subtable to record the no's and why they have happened. Rather
than have to click on the +sign to bring up the subtable is there anything I
can put in the field that when a no is recorded it automatically brings up
the subtable and will this work if I I make up a form?

Thanks for any help in advance.

Reply to this Message

Steve - 29 Jun 2007 03:38 GMT

Multiple tables is incorrect. You need:

TblOutcome
OutcomeID
OutcomeDate
OutcomeTime
IsAchieved (Yes/No)
Comment

On FrmOutcome, disable comment. Put the following code in the AfterUpdate
event of IsAchieved:
If Me!IsAchieved = True Then
Me!Comment.Enabled = True
Else
If Me!Comment Is Not Null Then
If MsgBox("Do You Want To Delete The Comment?",vbYesNo) = vbYes Then
Me!Comment = Null
End If
End If
Me!Comment.Enabled = False
End If

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
resource@pcdatasheet.com

>I have to create a database which monitors outcomes every four hours. I
>have
[quoted text clipped - 15 lines]
>
> Thanks for any help in advance.

Reply to this Message

JEM - 29 Jun 2007 23:28 GMT

Thanks for your advice. I'm fairly new to access so will try this out over
the weekend. Thanks again for taking the time to advice.

> Multiple tables is incorrect. You need:
>
[quoted text clipped - 42 lines]
> >
> > Thanks for any help in advance.

Reply to this Message

Jeff Boyce - 29 Jun 2007 20:33 GMT

As Steve points out, using multiple tables is treating Access as if it were
a spreadsheet. You'll get the best benefit of Access' features and
functions if you spend some time reading up on "normalization" (hint: this
isn't your grandmother's spreadsheet!).

If you want a table's field to, by default, start out with a value, you can
use the Default property to set that value. Note, however, that this will
only be applied to any new records after you set the Default.

If you are working directly in the tables ("click on the '+'..."), stop now!
Access tables store data, but Access forms give you some very handy ways to
display, enter, edit, etc. Working in tables also reinforces the (false)
impression that Access is just a spreadsheet.

Regards

Jeff Boyce
Microsoft Office/Access MVP

>I have to create a database which monitors outcomes every four hours. I
>have
[quoted text clipped - 15 lines]
>
> Thanks for any help in advance.

Reply to this Message

JEM - 29 Jun 2007 23:22 GMT

Thanks for you comments. I'm fairly new to access as you can probably guess.
I thought if I started in table form first to make sure it was working
before putting it in form view which I agree makes it easier to enter and
edit data.

> As Steve points out, using multiple tables is treating Access as if it were
> a spreadsheet. You'll get the best benefit of Access' features and
[quoted text clipped - 34 lines]
> >
> > Thanks for any help in advance.

Reply to this Message