Re: Please review this table design.
From: Fred Boer (fredboer1_at_NOyahooSPAM.com)
Date: 02/23/04
- Next message: Pavel Romashkin: "Re: Yes/No and default values"
- Previous message: Steve: "Re: Limitations of access"
- In reply to: Rick Willingham: "Re: Please review this table design."
- Next in thread: Rick Willingham: "Re: Please review this table design."
- Reply: Rick Willingham: "Re: Please review this table design."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 23 Feb 2004 13:17:46 -0500
Dear Rick:
You are obviously putting a lot of work into this! Good for you! Don't get
discouraged.... :)
> Thanks for taking the time, I really appreciate it.
No problem! However, when I say I'm not an expert, I'm *not* being modest! I
am glad you are taking a hard look at normalization, but I am afraid that I
am not skilled enough to be of much more help, for fear of giving you bad
advice! :(
However, I'll say this much...
> I have three calculation fields: HoursWorked, JobCommissionAmount, and
EndOfResponsibilityDate. Of the three, I want to save the value rather than
update the value if there is a future commission rate change.
I don't know enough about this to help, but I *have* often seen posts about
this issue, and the suggestion is usually to add data/time field to the
record, so that if there are any future changes, the changes can be
calculated using these date/time fields... but you might want to do a Google
search of the Access newsgroups..
>I already have update queries to calculate the values, macros that run the
queries, and forms with text boxes that display the info. I think I read
that the form field can be programmed to calculate the value and so the
macros and the queries aren't needed.
Yes, that is true.. A control on a form can use a calculation as the source
of the data it displays..
>I guess the question here is: Should I re-build all of those objects
before going further (hours of redo work...ugh!) or will having those fields
really hurt anything now or down the line?
I really don't think I am in any position to tell you what to do, but, if I
was to go out on a limb, I'd suggest that hours of redo work now might save
you days of redo work later....
> tblTimeClock seems like it is two subjects, but I couldn't do the
split/re-join test (in my head) and not loose data. The
<snipped>
> I left my list of 'errors' at home, and I can't remember if I that's all
of them or not.
>
> Rick...
Sorry, Rick, but I really *don't* have the skill set to help you with the
rest of this... I'd like to help but (insert Clint Eastwood-type muttering
voice) "a man's got to know his limitations...".
I suggest that you continue to read newsgroups, try doing searches in Google
Groups, and continue to post questions. Have you read the netiquette for the
newsgroup? It has useful information on how to best frame your questions to
get useful responses... http://www.mvps.org/access/netiquette.htm (It says
its for CDMA, but it applies here, too..) And, with any luck, someone who
really does know his/her stuff will help you!
Good Luck!
Fred
- Next message: Pavel Romashkin: "Re: Yes/No and default values"
- Previous message: Steve: "Re: Limitations of access"
- In reply to: Rick Willingham: "Re: Please review this table design."
- Next in thread: Rick Willingham: "Re: Please review this table design."
- Reply: Rick Willingham: "Re: Please review this table design."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|