New Database
From: Lisa Reber (anonymous_at_discussions.microsoft.com)
Date: 02/26/04
- Next message: Duane Hookom: "Re: Schedule App Outline (was Re: Scheduling database: basic data structure?)"
- Previous message: James Gifford: "Re: Schedule App Outline (was Re: Scheduling database: basic data structure?)"
- In reply to: Judy Martin: "New Database"
- Next in thread: Rolls: "Re: New Database"
- Reply: Rolls: "Re: New Database"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Feb 2004 10:38:23 -0800
Hi - I'm a novice too, so you might be ahead of me
already. I have a number of posts below about my
(partially-inherited) poor table design. Here's a couple
thing I'd do over - don't put any spaces in your field
names, just in the captions. Second, check out MS
Knowledgebase article 100139 on Database Normalization
Basics (will help with Rolls' reply). Third, when you
create your database objects, name them according to
object type, like tblClient, tblSubscriber, frmOrders,
etc. It's supposed to be good practice, and it does (or it
would have) help on those days when my brain is
overloaded. Finally, and it's what sent me here in the
first place, be sure you have good/correct relationships
set up before entering any permanent data! Rolls sent me a
good reply on a question I had, but it took me a while to
figure out that PK = Primary Key, and FK = foreigh key.
Like I said, maybe you're ahead of me so this is redundant.
Good luck! - Lisa
>-----Original Message-----
>I am a novice to Access!
>
>I have to start a database for the publishing company
>that I work for. We sell books via subscription ie
>clients pay a nominal deposit to secure an order on a
>book and have their name on a subscribers page in the
>book and then pay the balance about 1 month before
>publication. The book is sight unseen when they pay. The
>databse headings I need are as follows:
>
>CLIENT ID; TITLE; INITIAL; SURNAME; SALUATION; ADDRESS1;
>ADDRESS2; ADDRESS3; ADDRESS4; ADDRESS5; POST CODE;
>COUNTRY; TELEPHONE; EMAIL
>
>PAYMENT METHOD; CC TYPE; CC NUMBER; CC EXPIRY; QUANTITY;
>AMOUNT; DEPOSIT; BALANCE; SHIPPING COST
>
>SUBSCRIBER NO; SUBSCRIBER BOOK TITLE; SUBSCRIBER FIRST
>NAME; SUBSCRIBER SURNAME; SUBSCRIBER LOCATION; DELIVERY
>NAME; DELIVERY ADDRESS1; DELIVERY ADDRESS2; DELIVERY
>ADDRESS3; DELIVERY ADDRESS4; DELIVERY ADDRESS5; DELIVERY
>POST CODE; DELIVERY COUNTRY; SHIPPING
>
>SOURCE; ENTRY DATE; FREE GIFT; COMMENTS; SALES HISTORY;
>VETTED ORG
>
>Should they be, as grouped above, in 4 tables? How do I
>linked them together so that if I click on a certain
>client (using Client ID presumably) all the data from the
>other tables will be visable.
>
>Is it possible to have toggle links on the form of the
>Clients Database, first of the above groups, so that I
>could see other data related to any one Client? Or would
>it be better to have 4 Tab forms?
>
>Sorry that this is so long winded, I did say at the
>beginning that I am new to this.
>
>Thanks to anyone who might be in a position to help me. I
>would be eternally grateful.
>
>Jude
>.
>
- Next message: Duane Hookom: "Re: Schedule App Outline (was Re: Scheduling database: basic data structure?)"
- Previous message: James Gifford: "Re: Schedule App Outline (was Re: Scheduling database: basic data structure?)"
- In reply to: Judy Martin: "New Database"
- Next in thread: Rolls: "Re: New Database"
- Reply: Rolls: "Re: New Database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|