What are these fields for:
Maintenance
Recalls
Keepers
Secondary
I wonder if this structure is un-normalized.
Duane Hookom
MS Access MVP
To: AccessDevelopers@yahoogroups.com
From: mossj5@comcast.net
Date: Thu, 31 May 2012 17:54:10 -0600
Subject: Re: [AccessDevelopers] New DB Design Ideas
Maintenance
Recalls
Keepers
Secondary
I wonder if this structure is un-normalized.
Duane Hookom
MS Access MVP
To: AccessDevelopers@yahoogroups.com
From: mossj5@comcast.net
Date: Thu, 31 May 2012 17:54:10 -0600
Subject: Re: [AccessDevelopers] New DB Design Ideas
Toby,
Here's the data each file may or may not have:
Transaction Count
Session #
Amount
Maintenance
Recalls
Keepers
Secondary
If I use a single table with a field for each entry, I'll end up with empty fields. For example, if file one has these fields:
Transaction Count
Session #
Amount
Maintenance
Recalls
Keepers
and file 2 has these fields
Maintenance
Recalls
Keepers
and file 3 has this field
Secondary
then the first set of fields will be empty for file 3 and there will be empty fields for file 2..
But as I type and think this through that may not be a bad idea. That way you'll know if the file had only transaction or transactions and maintenance. A Null valuewould mean either no data was entered or it was missed.
Does that make sense?
Thanks,
John
On 5/31/2012 4:05 PM, Toby Bierly wrote:
Here's the data each file may or may not have:
Transaction Count
Session #
Amount
Maintenance
Recalls
Keepers
Secondary
If I use a single table with a field for each entry, I'll end up with empty fields. For example, if file one has these fields:
Transaction Count
Session #
Amount
Maintenance
Recalls
Keepers
and file 2 has these fields
Maintenance
Recalls
Keepers
and file 3 has this field
Secondary
then the first set of fields will be empty for file 3 and there will be empty fields for file 2..
But as I type and think this through that may not be a bad idea. That way you'll know if the file had only transaction or transactions and maintenance. A Null valuewould mean either no data was entered or it was missed.
Does that make sense?
Thanks,
John
On 5/31/2012 4:05 PM, Toby Bierly wrote:
You should be able to setup a table with the following fields:Date, Client, File_Name, Count, Transaction_Number, Amount, etc.You would enter multiple files on any given date, and record the client it was for, and the other info you specified.I'm not sure how you are ending up with empty rows.Hope this helps,Toby-----Original Message-----
From: AccessDevelopers@yahoogroups.com [mailto:AccessDevelopers@yahoogroups.com] On Behalf Of yshopper
Sent: Thursday, May 31, 2012 1:29 PM
To: AccessDevelopers@yahoogroups.com
Subject: [AccessDevelopers] New DB Design Ideas
I am starting a new project that will track Daily Tasks. One of the tasks is to download and process files. Each day the number of files will change. I need to record the name of the file and several other pieces of info after the file is processed; i.e. Count, Transaction Number, Amount, etc.
Some days there will be only 10-12 files, other days there could be upwards of 70-75 files. I need to record each file for each day. Also, these files are associated with 3 different clients.
How would I design a table(s) that will allow this type of data? I have a DB setup but it ends up with empty rows on all but the busiest days. I would like to avoid that if possible.
Thanks for any tips or suggestions,
John
__._,_.___
Please zip all files prior to uploading to Files section.
.
__,_._,___
Tidak ada komentar:
Posting Komentar