Re: Access is just to hard to understand

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks Bob


>>Tom
>
>The first thing I would do is decide what you want your database to do,
>decide what data you need to do it, and then, design the tables (all without
>even opening Access.)
>For example: You want to be able to look up contacts phone #'s and addresses
>and print mailing labels.
>You will probably want last name, first name, middle initial, street address
>(for FedEx, etc.), mailing address, city, state, zip, phone number.
>In this example you will need only one table that will have all of the above
>fields.
>Now open Access and a new blank db. When asked, name it Contacts or
>Contacts_be. The be stands for back end. I recommend that you create a
>backend db for tables that will be shared by users. Each user can link to
>the backend db tables.
>Select New on the Tables tab of your db. I recommend Design View so you can
>control all aspects of the design.
>In the first Field Name blank type LastName (It is best that all names have
>no blanks, that way if you ever convert to SQL you're set), press Tab and
>type t (Text will appear). Continue with the rest and you have your table.
>Save it with a logical name like Contacts.
>For queries, forms, and reports use the wizards.


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-gettingstarted/200508/1
.

Relevant Pages

  • Re: Access is just to hard to understand
    ... >>backend db for tables that will be shared by users. ... I recommend Design View so you can ... >>no blanks, that way if you ever convert to SQL you're set), press Tab and ...
    (microsoft.public.access.gettingstarted)
  • Re: Access is just to hard to understand
    ... Tom wrote: ... backend db for tables that will be shared by users. ... I recommend Design View so you can ... no blanks, that way if you ever convert to SQL you're set), press Tab and ...
    (microsoft.public.access.gettingstarted)
  • Re: Form with 11 cmbo boxes - very slow to save design changes
    ... > Our app has a front end with the forms and a backend with the linked data. ... > This form takes a huge amount of time to save changes during design, ... > this long to save design changes to, ... > which have combo boxes. ...
    (microsoft.public.access.forms)
  • Re: Internet synchronization
    ... If you are referring to design work, you should just split the database ... objects and is linked to the tables in the backend. ... the frontend can link to it while you make design changes. ...
    (microsoft.public.access.externaldata)
  • Re: Move old records to other table
    ... >>Do I need to move the split table to other database under this design? ... I'd suggest creating a second backend database on the server. ... and recreating the indexes and compacting again. ...
    (microsoft.public.access.tablesdbdesign)