新手应该先学习什么? [英] what should a novice learn first

查看:54
本文介绍了新手应该先学习什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好吧


这个wkend似乎是一个msaccess的心情。我今年拒绝参加暑期学校,把更多时间花在数据库上,但我们可以肯定已经用过这笔钱了,猜猜谁让我想起了这个,以及谁又被重新考虑了。对于那些踢股票和股息的人来说,给任何浓缩咖啡制造商都要花一些钱。我们必须从我们自己的小居所中融资一半的红利!


我开始阅读不同的帖子,我看到sql像6月份的蒲公英一样频繁出现。所以作为一个新手,我开始认为也许我应该调查sql除了基本的表/表单设计,然后我想好吧也许我应该介绍sql明年我的学生,如果我教的编程类,这是刚刚获得但可能可能会将它们与他们无法真正使用的高级概念混淆。这个班级将是6年级学生。


所以,我想我需要一些帮助来获得学习方向。还有这么多要学的东西,我应该如何决定现在应该做什么,以后应该做些什么呢?


顺便说一下,似乎有一个核心的专业人士是这里的主力者和谁我一直在与getgo互动。我很幸运能够登陆这里,特别是因为这是我登陆的第一个论坛。


欢呼!

解决方案

嗨莫莉,

这是一个关于字节)谈论数据库规范化。它可以真正成为一个外国概念,但理解它可以为你节省数千小时的头痛和返工 - 我说的是一个学习了很长很难的方法 设计数据库。 PhilOfWalton也有一篇很好的文章(Word Doc),我知道他愿意与你分享。


奇怪的是,我要去学习的第二个地方是正确的命名约定(任何其他专家可以在这里自由地反对我。)但是,在设计数据库时,您希望将对象命名为有意义的,不太长的,避免关键词或限制词 AND 是DB可以轻松使用的东西。谷歌搜索数据库命名约定,你会得到一些好主意。没有正确的命名计划,但只需选择一个并坚持下去。例如,在您的原始帖子中,我的假设是您不会将文本框命名为与您的某个字段相同,而是txtFieldName。这对我来说是一种疏忽,因为对于我来说,将控件添加到表单/报表并为其指定一个正确的名称(包括我的所有标签)是第二天性。同样,从长远来看,这样做可以省去头痛。


第三,您将希望基本了解查询是什么,它们如何工作,如何连接表,如何在查询中使用条件并彻底理解布尔逻辑(这是查询如何确定其标准。您最初不需要成为查询专家(SQL),但您需要了解基础知识。其中一个最聪明SQL中这个论坛上的家伙是Rabbit。留意他的回答并仔细吸收他们。他的回答很简短,但我真的理解如何构建查询。我从他那里学到了很多东西。


第四,避免使用宏;了解VBA的基础知识。在我看来,宏是非常有限的并且不是编程。作为一个附加的指南,为你创建的每个过程添加错误处理(你可以搜索对于基础知识,我会发布一个快速简单的子工作,你可以在我上班时使用。)


我最好的建议是考虑ab你要做什么(例如,我想根据另一个文本框的值改变文本框的值。)并完成如何做到这一点的宝贝步骤:
< ol style =list-style-type:decimal>
  • 我需要第一个文本框的值
  • 我需要检查这是否是有效值
  • I需要操纵该值
  • 我需要确保结果有效
  • 我需要将该值分配给新文本框


  • 随着时间的推移,宝宝的步骤会很自然地出现,然后你会扩大你的理解。


    始终牢记这一点: 没有人 在这个网站上成为专家一夜之间。我鼓励你去我的个人资料,看看我最老的帖子。我会认为自己是一个菜鸟,即使我这样做是为了谋生。 NeoPa,zmbd,Rabbit,PhilOfWalton和其他人教会了我很多。请耐心等待,但要致力于学习和信任专家试图教给你的东西。如果你不理解一个概念,请问。我已经多次要求澄清了,答案总能帮助我更全面地了解我的工艺。


    我相信还有更多可以遵循。


    你为我的想法提供了一分钱,我扔了两美分。


    希望这个hepps!


    Hi Molly


    我将以与Twinnyfo完全相同的方式回复。


    我要添加的唯一补充是与正确的表格设计一起,你需要建立表之间的关系。

    必须才能做到这一点,因为这是数据库的基础。你不能在狡猾的基础上建房子并期望它能够持久。


    我相信如果你看过关于字节的各种问题,那么很多都是由不正确的表结构。


    twinnyfo的回复的另一个补充是在表单或报表上使用正确的控件描述。最近我们有了名为Tabs和Pages的命令按钮,称为Tabs或Tab Controls。在 https://bytes.com/topic/access/上发布18回答......-某些页面可能有所帮助。


    这是我对规范化的可怜努力。请参阅第9页上的第9页

    https://bytes.com/topic/access/answe...ent-field-null


    Phil


    As前面提到过,在一个新的独立VBA模块中放入以下内容并保存:

    展开 | 选择 | Wrap | 行号


    hi everyone

    i seem to be in an msaccess mood this wkend. i turned down doing summer school this year to devote more time to databases but we could sure have used the money, guess who reminded me of that and who is espessoed out again. btw to those kicking the stocks and dividends thing around, put some bucks into any espresso mfr. we must be financing half the dividends right from our own little abode!

    i get a kick out of reading the different posts and i see sql popping up as often as dandelions in june. so as a novice i begin to think maybe i should investigate sql in addition to basic table/form design and then i think well maybe i should introduce sql to my students next year if i teach the programming class which is just about clinched but that could possibly confuse them with advanced concepts they cant really use. the class will be 6th graders.

    so, i think i need some help getting a direction for study here. theres so much to learn, how should i decide what should be now and what should be later?

    also btw it seems there is a core group of pros who are the workhorses here and who ive been interacting with from the getgo. i feel lucky to have landed here, especially since this is the first forum ive ever landed in.

    cheers!

    解决方案

    Hi Molly,

    From a very, very basic perspective, what you should learn first is proper table design. There are a plethora of articles (here is one on Bytes) that talk about Database Normalization. It can truly be a foreign concept, but understanding it well can save you thousands of hours in headaches and rework—I speak as one who learned the long, hard way how NOT to design a database. PhilOfWalton also has a good article (Word Doc) that I know he is willing to share with you.

    Oddly enough, the second place I would go for learning is proper naming conventions (any of the other experts are free to disagree with me here). However, when designing a database, you want to name your objects something that makes sense, is not too long, avoids key words or restricted words AND is something the DB can use easily. Do a Google search for database naming conventions and you will gets some good ideas. There are no “right” naming plans, but just choose one and stick with it. For example, in your original post, my assumption was that you would not have text box named the same as one of your fields, but rather “txtFieldName”. That was an oversight on my part, because it is second nature for me to add a control to a form/report and assign it a proper name (including all my labels). Again, doing this will save you headaches in the long run.

    Third, you will want to get a basic understanding of what queries are, how they work, how tables can be JOINED, how to use criteria in queries and a thorough understanding of Boolean logic (which is how queries determine their criteria. You do not need to be an expert in queries (SQL) at first, but you need to understand the basics. One of the smartest dudes on this forum in SQL is Rabbit. Keep an eye out for his responses and absorb them carefully. He is brief in his responses, but really understands how to build a query. I’ve learned a lot from him.

    Fourth, avoid macros; learn the basics of VBA. Macros are incredibly limited and are NOT programming, in my opinion. As an added guideline, add error handling to every single procedure you create (you can search for the basics and I will post a quick and easy sub you can use when I get to work).

    My best advice is to think about what you want to do (e.g., “I want to change the value of a text box based upon the value of a another text box.”) and work through the baby steps of how you would do that:

    1. I need the value of the first text box
    2. I need to check that this is a valid value
    3. I need to manipulate that value
    4. I need to make sure the result is valid
    5. I need to assign that value to the new text box


    Over time the baby steps will come naturally, then you will expand your understanding.

    Always keep this in mind: NO ONE on this site became experts overnight. I encourage you to go to my profile and look at my oldest posts. I would have considered myself a noob, even though I was doing this for a living. NeoPa, zmbd, Rabbit, PhilOfWalton and others have taught me much. Be patient with yourselves, but be committed to learning and trusting what the experts are trying to teach you. If you don’t understand a concept, ask. I’ve asked for clarification many times, and the answer always helps me understand my craft more fully.

    I am sure there is more to follow.

    You offered a penny for my thoughts, and I threw my two cents in.

    Hope this hepps!


    Hi Molly

    I was going to reply in exactly the same way as Twinnyfo.

    The only addition I would add is that together with correct table design, you need to set up the relationships between tables.
    You must get this right as this is the foundation for a database. You can''t build a house on dodgy foundations and expect it to last.

    I am sure if you have looked at various questions on Bytes, so many of them are caused by incorrect table structures.

    The other addition to twinnyfo''s reply is to use the correct description of controls on a form or report. Recently we have had Command Buttons called Tabs and Pages called Tabs or Tab Controls. Post 18 onhttps://bytes.com/topic/access/answe...-certain-pages might help.

    Here is my pathetic effort on normalisation. See post no 9 on

    https://bytes.com/topic/access/answe...ent-field-null

    Phil


    As mentioned earlier, in a new standalone VBA module put the following and save it:

    Expand|Select|Wrap|Line Numbers


    这篇关于新手应该先学习什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

    查看全文
    登录 关闭
    扫码关注1秒登录
    发送“验证码”获取 | 15天全站免登陆