Hi John,
I've been studying as I go along, but I did just start out knowing nothing,
and Access is a challenge! ;-) I did download Crystal's excellent beginners
info from the group files and now that I have new speakers for my computer I
will watch the videos, thank you for the link!
I am using Access XP, so it is fairly old. I am considering upgrading to
2010 but can't afford it right now...
I'm understanding now that I cannot store the calculated values in the table
itself, but is there a way to enter that information onto a form and have it
show up? I think the easiest way to explain what I mean is to send you a
PDF page of an example of what I am trying to do.. Can I send attachments
to the list or would it be best to upload it to the files?
I found the index in table design, thanks! Will put part_number in the
parts_purchase table and see how that works!
Again, thank you for all of your assistance and patience! I am learning
alot and I really appreciate all of your help!
Deb
On Mon, Jul 25, 2011 at 1:07 AM, John Viescas <john@viescas.com> wrote:
> Deb-
>
> Oh, my. Have you done any studying at all? Unlike the other Office apps,
> you
> can't just start up Access and start using it with no knowledge of
> databases.
> Well, you can load up one of the many templates if one meets your needs and
> muddle along that way. But you cannot expect to start building something
> from
> scratch and be successful. Please at least go watch Crystal's excellent
> introductory videos on YouTube:
>
> http://www.youtube.com/user/LearnAccessByCrystal
>
> 3-5: It's "against the rules" in design of a Relational Database to store
> ANY
> calculated values. You don't say which version of Access you have, but
> only the
> very latest version (2010) finally allows you to "store" calculated values.
> You
> define those calculated fields in the table design, not in an expression on
> a
> form. If you have an earlier version (which I suspect is true because you
> uploaded an MDB file), you can certainly calculate values you need on the
> fly in
> a query or control expression, but you cannot and should not attempt to
> store
> the values in the tables.
>
> You define indexes in Table Design. I told you to link on Part_Number, so
> you
> need a copy of Part_Number in the Parts_Purchase table. Part_Number in the
> Parts_Inventory table must either be the Primary Key or it must have an
> index -
> indexed, no duplicates.
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> http://www.viescas.com/
> (Paris, France)
>
>
>
[Non-text portions of this message have been removed]
Tidak ada komentar:
Posting Komentar