G
Guest
what is the best way to create a client data base from scratch. "L" plater
here.
here.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
missinglinq via AccessMonster.com
I take it from your question that you're new to this and will probably be
coming back here often, so one word of advice: Most of us are here because we
want to help other people with our knowledge, which is as varied in depth and
scope as the number of members themselves. What we are not are soothsayers!
We are dependent on you telling us, in a clear manner, what you're trying to
do, what you've already tried and why/how it hasn't worked. If you have code
that's bombed, post the code and the errror messages and any other revelvant
information. Because everyone here are volunteers, we get here and look
around when we can; many games of "posting tag" are played. If you give all
of the above listed items in your initial post it'll greatly speed up your
getting help.
Point in question: Are you trying to create a database for a client, or a
database to track your own clients?
1) General planning
The single most important phase of any software development is PLANNING!
Before you ever sit down at your computer, take pen and paper and outline
what you want to accomplish with your db. It's far easier to plan from the
beginning everything you want to do, than to start making major revisions
before you ever have the thing up and running!
2) Identify and define your data
Make a list of all the data you'll need to accomplish and what kind of data
it is. A good thing to remember is that numerical data types (Integer, Long,
Single, Double, etc) should only be used if they are going to be used in
mathematical calculations! Data that is composed of digits, such as telephone
numbers, ID numbers, SSNs, etc but are not used for math should be defined as
text! Text data is much easier to manipulate!
3) Data grouping
Once you have a listing of the data you'll need, divide it up into logical
groups. In Access these are groups are called Tables. At this point you need
to start thinking about the relationships between these tables. Each record
of each table should have a Primary Key, a field that is unique to that one
Record. An example when working with records of people would be a Social
Security Number. No two persons ever have the same SSN. In order for tables
to to work together they must "relate" or have at least one field in common.
4) Task List
Break up things listed in # 1 above into smaller, more manageable tasks. I
always keep a pad just to make notes of tasks or routines I need to
accomplish; quarterly checkups based on initial setup dates, reminders when
invoices are overdue, etc.
The general order of creation of objects in Access should be:
1) Tables
2) Queries
3) Forms
That's a very broad outline of the creation of a database by me, The
Missinglinq. I'm sure there'll be others! As my signature says "There's
ALWAYS more than one way to skin the cat!
coming back here often, so one word of advice: Most of us are here because we
want to help other people with our knowledge, which is as varied in depth and
scope as the number of members themselves. What we are not are soothsayers!
We are dependent on you telling us, in a clear manner, what you're trying to
do, what you've already tried and why/how it hasn't worked. If you have code
that's bombed, post the code and the errror messages and any other revelvant
information. Because everyone here are volunteers, we get here and look
around when we can; many games of "posting tag" are played. If you give all
of the above listed items in your initial post it'll greatly speed up your
getting help.
Point in question: Are you trying to create a database for a client, or a
database to track your own clients?
1) General planning
The single most important phase of any software development is PLANNING!
Before you ever sit down at your computer, take pen and paper and outline
what you want to accomplish with your db. It's far easier to plan from the
beginning everything you want to do, than to start making major revisions
before you ever have the thing up and running!
2) Identify and define your data
Make a list of all the data you'll need to accomplish and what kind of data
it is. A good thing to remember is that numerical data types (Integer, Long,
Single, Double, etc) should only be used if they are going to be used in
mathematical calculations! Data that is composed of digits, such as telephone
numbers, ID numbers, SSNs, etc but are not used for math should be defined as
text! Text data is much easier to manipulate!
3) Data grouping
Once you have a listing of the data you'll need, divide it up into logical
groups. In Access these are groups are called Tables. At this point you need
to start thinking about the relationships between these tables. Each record
of each table should have a Primary Key, a field that is unique to that one
Record. An example when working with records of people would be a Social
Security Number. No two persons ever have the same SSN. In order for tables
to to work together they must "relate" or have at least one field in common.
4) Task List
Break up things listed in # 1 above into smaller, more manageable tasks. I
always keep a pad just to make notes of tasks or routines I need to
accomplish; quarterly checkups based on initial setup dates, reminders when
invoices are overdue, etc.
The general order of creation of objects in Access should be:
1) Tables
2) Queries
3) Forms
That's a very broad outline of the creation of a database by me, The
Missinglinq. I'm sure there'll be others! As my signature says "There's
ALWAYS more than one way to skin the cat!
G
Guest
What is posting tag
around when we can; many games of "posting tag" are played. If you give all
D
Douglas J. Steele
Person A posts a question, Person B asks followup questions, Person A
answers some, but not all of the followup questions, Person B tries to get
more details, and so it goes.
answers some, but not all of the followup questions, Person B tries to get
more details, and so it goes.
M
missinglinq via AccessMonster.com
Exactly! You can spend a day or two before the people here have all the info
needed to address the original question! Much easier if the OP (Original
Poster) gives all the needed info up front!
--
There's ALWAYS more than one way to skin a cat!
Answers/posts based on Access 2000
Message posted via AccessMonster.com
needed to address the original question! Much easier if the OP (Original
Poster) gives all the needed info up front!
Person A posts a question, Person B asks followup questions, Person A
answers some, but not all of the followup questions, Person B tries to get
more details, and so it goes.
--
There's ALWAYS more than one way to skin a cat!
Answers/posts based on Access 2000
Message posted via AccessMonster.com
G
Guest
Bron
have a look at the database templates available at Microsoft/Office. com.
I'm sure there is a Contact Management database that may suit your needs.
have a look at the database templates available at Microsoft/Office. com.
I'm sure there is a Contact Management database that may suit your needs.
G
Guest
Thanks Douuglas and Mr Misslngling (??)
Sorry not to understand but (a9As I used to put below my name) scusate,ma il
mio Inglese fa schiffo.
But I took this off before one of the forum censors worked out what it means
in English Ha Ha Ha
A rough translation would be
Excuse me but my English is ****
Sorry not to understand but (a9As I used to put below my name) scusate,ma il
mio Inglese fa schiffo.
But I took this off before one of the forum censors worked out what it means
in English Ha Ha Ha
A rough translation would be
Excuse me but my English is ****