A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » New Users
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Unbound fields



 
 
Thread Tools Display Modes
  #11  
Old August 22nd, 2007, 09:18 AM posted to microsoft.public.access.gettingstarted
Rhianne
external usenet poster
 
Posts: 85
Default Unbound fields

My database is for Personnel Records, it contains information that records
all staff's personal details and also training info, hours worked etc.

I would like to point out that I am now more confused than when I began!

I have looked at my table and it seems that quite a few of my fields on my
form are missing from the table - so do I need to add them into it? And will
they be paired up to what is showing on my form?

Thanks for the help! Much much apreciated!

"John W. Vinson" wrote:

On Tue, 21 Aug 2007 08:32:05 -0700, Rhianne
wrote:

So do I simply add a new field to my table? don't need to concern myself
with the form so much?


Many folks fall into the trap you're in.

The thing to realize is that the Form, although very important, is decidedly
SECONDARY.

The data in your database isn't in your form. It's in the Table, and only in
the Table. A properly normalized set of tables is like the foundation of a
house; if it's incomplete, or incorrectly designed, your whole house can come
tumbling down!

The Form is *just a window* - a tool to let you view and edit data in the
tables. Adding a textbox to a form does NOT let you store data permanently;
again - it's just a window, and if there's no room behind the window, you
can't do anything with it.

Since you're just getting started, it would be really important to make sure
your table structures are right FIRST, and then adapt the form to the tables
(rather than vice versa). Check out the references below (especially the
Database Design 101 links on Jeff's site, and Crystal's tutorial), and don't
hesitate to post back here with a description of your database: what's its
purpose, what information does it manage, and the structures of your tables.

John W. Vinson [MVP]

  #12  
Old August 22nd, 2007, 12:38 PM posted to microsoft.public.access.gettingstarted
Rhianne
external usenet poster
 
Posts: 85
Default Unbound fields

I have now successfully made all my field bound to my table.

Is this is it? Or will I need to do anything else to be able to save each
individual record?


"John W. Vinson" wrote:

On Tue, 21 Aug 2007 08:32:05 -0700, Rhianne
wrote:

So do I simply add a new field to my table? don't need to concern myself
with the form so much?


Many folks fall into the trap you're in.

The thing to realize is that the Form, although very important, is decidedly
SECONDARY.

The data in your database isn't in your form. It's in the Table, and only in
the Table. A properly normalized set of tables is like the foundation of a
house; if it's incomplete, or incorrectly designed, your whole house can come
tumbling down!

The Form is *just a window* - a tool to let you view and edit data in the
tables. Adding a textbox to a form does NOT let you store data permanently;
again - it's just a window, and if there's no room behind the window, you
can't do anything with it.

Since you're just getting started, it would be really important to make sure
your table structures are right FIRST, and then adapt the form to the tables
(rather than vice versa). Check out the references below (especially the
Database Design 101 links on Jeff's site, and Crystal's tutorial), and don't
hesitate to post back here with a description of your database: what's its
purpose, what information does it manage, and the structures of your tables.

John W. Vinson [MVP]

  #13  
Old August 22nd, 2007, 12:45 PM posted to microsoft.public.access.gettingstarted
John Spencer
external usenet poster
 
Posts: 7,815
Default Unbound fields

Yes, you need to add the fields to the table.

If your form is based on the table (and not a query of the table) the fields
should become available. If your form is based on a query (which I think is
best), then you will probably need to open the query and add the fields to
the query.

You can open the query by clicking on the small button next to record source
in the form's property dialog.

Tables (and fields) are for storing data
Queries are for selecting data that is stored in tables
Forms are for displaying, entering, and changing data from queries or tables
Reports are for printing data

--
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
..

"Rhianne" wrote in message
...
My database is for Personnel Records, it contains information that records
all staff's personal details and also training info, hours worked etc.

I would like to point out that I am now more confused than when I began!

I have looked at my table and it seems that quite a few of my fields on my
form are missing from the table - so do I need to add them into it? And
will
they be paired up to what is showing on my form?

Thanks for the help! Much much apreciated!

"John W. Vinson" wrote:

On Tue, 21 Aug 2007 08:32:05 -0700, Rhianne
wrote:

So do I simply add a new field to my table? don't need to concern
myself
with the form so much?


Many folks fall into the trap you're in.

The thing to realize is that the Form, although very important, is
decidedly
SECONDARY.

The data in your database isn't in your form. It's in the Table, and only
in
the Table. A properly normalized set of tables is like the foundation of
a
house; if it's incomplete, or incorrectly designed, your whole house can
come
tumbling down!

The Form is *just a window* - a tool to let you view and edit data in the
tables. Adding a textbox to a form does NOT let you store data
permanently;
again - it's just a window, and if there's no room behind the window, you
can't do anything with it.

Since you're just getting started, it would be really important to make
sure
your table structures are right FIRST, and then adapt the form to the
tables
(rather than vice versa). Check out the references below (especially the
Database Design 101 links on Jeff's site, and Crystal's tutorial), and
don't
hesitate to post back here with a description of your database: what's
its
purpose, what information does it manage, and the structures of your
tables.

John W. Vinson [MVP]



  #14  
Old August 22nd, 2007, 02:06 PM posted to microsoft.public.access.gettingstarted
Rhianne
external usenet poster
 
Posts: 85
Default Unbound fields

I have added the fields into my table and they are now bound fields. However,
is it best for me to also create a query as well?

Thanks!

"Rhianne" wrote:

I am new to access and am teaching myself how to create one. I grasp the idea
of fields and control sources, but I have fields that need to contain data
that do not have appropriate control sources - I think it was my own fault
for not inputting enough when I first created the form. So now I have at six
fields that are unbound, I have tried linking them to control sources that
are already linked to another field, but of course that doesnt' work.
Ideally, I would like to add in extra field names (to be renamed by myself),
that will not have to be controlled by sources that are controlling another
field. Otherwise it is the text or number is duplicated in both fields.
How can I rectify this problem? I do not understand much of the terminology
used in access, so in laymen's terms please!!

  #15  
Old August 22nd, 2007, 05:01 PM posted to microsoft.public.access.gettingstarted
James Ivey[_3_]
external usenet poster
 
Posts: 23
Default Unbound fields

Hi Rhianne,

I am very new to Access as well.. just a couple of months into it. But I've
gotten lots of great help here in this newsgroup. Here is one piece of
advice I followed (someone please correct me if I'm wrong!):

For my simple membership database I have just one table and one query (at
the moment)

First, create your tables with all the fields you need
Second, create your queries based on your tables.
Third, create your forms based on your queries.

I was told its best to do it that way because it will be easier to maintain
when your database becomes more complex.

Hope that helps,
James



"Rhianne" wrote in message
...
I have added the fields into my table and they are now bound fields.
However,
is it best for me to also create a query as well?

Thanks!

"Rhianne" wrote:

I am new to access and am teaching myself how to create one. I grasp the
idea
of fields and control sources, but I have fields that need to contain
data
that do not have appropriate control sources - I think it was my own
fault
for not inputting enough when I first created the form. So now I have at
six
fields that are unbound, I have tried linking them to control sources
that
are already linked to another field, but of course that doesnt' work.
Ideally, I would like to add in extra field names (to be renamed by
myself),
that will not have to be controlled by sources that are controlling
another
field. Otherwise it is the text or number is duplicated in both fields.
How can I rectify this problem? I do not understand much of the
terminology
used in access, so in laymen's terms please!!




  #16  
Old August 22nd, 2007, 05:13 PM posted to microsoft.public.access.gettingstarted
John W. Vinson
external usenet poster
 
Posts: 18,261
Default Unbound fields

On Wed, 22 Aug 2007 04:38:00 -0700, Rhianne
wrote:

I have now successfully made all my field bound to my table.

Is this is it? Or will I need to do anything else to be able to save each
individual record?


Since you haven't said what you've done, nor how your form is set up, all I
can say is "I hope so".

If the Table is correctly set up with all the fields that you need, and each
of those fields is bound to a control on the form, then you do not need to do
anything extra to save records. Access will save the record as soon as you
move to a different record, close the form, or do something else to explicitly
save the record.

John W. Vinson [MVP]
  #17  
Old August 22nd, 2007, 05:15 PM posted to microsoft.public.access.gettingstarted
John W. Vinson
external usenet poster
 
Posts: 18,261
Default Unbound fields

On Wed, 22 Aug 2007 06:06:01 -0700, Rhianne
wrote:

I have added the fields into my table and they are now bound fields. However,
is it best for me to also create a query as well?


If you need one, yes; if you don't need one, no. It's very certain that as
your database develops you will be creating queries but whether you need one
right now isn't a question any of us, far away from your computer, can answer!

John W. Vinson [MVP]
  #18  
Old August 23rd, 2007, 09:20 AM posted to microsoft.public.access.gettingstarted
Rhianne
external usenet poster
 
Posts: 85
Default Unbound fields

well, what is the purpose of a query? If I knew that then I could decide if I
need one or not.

"John W. Vinson" wrote:

On Wed, 22 Aug 2007 06:06:01 -0700, Rhianne
wrote:

I have added the fields into my table and they are now bound fields. However,
is it best for me to also create a query as well?


If you need one, yes; if you don't need one, no. It's very certain that as
your database develops you will be creating queries but whether you need one
right now isn't a question any of us, far away from your computer, can answer!

John W. Vinson [MVP]

  #19  
Old August 23rd, 2007, 09:22 AM posted to microsoft.public.access.gettingstarted
Rhianne
external usenet poster
 
Posts: 85
Default Unbound fields

cheers for that! But what exactly are the purpose of queries?

"James Ivey" wrote:

Hi Rhianne,

I am very new to Access as well.. just a couple of months into it. But I've
gotten lots of great help here in this newsgroup. Here is one piece of
advice I followed (someone please correct me if I'm wrong!):

For my simple membership database I have just one table and one query (at
the moment)

First, create your tables with all the fields you need
Second, create your queries based on your tables.
Third, create your forms based on your queries.

I was told its best to do it that way because it will be easier to maintain
when your database becomes more complex.

Hope that helps,
James



"Rhianne" wrote in message
...
I have added the fields into my table and they are now bound fields.
However,
is it best for me to also create a query as well?

Thanks!

"Rhianne" wrote:

I am new to access and am teaching myself how to create one. I grasp the
idea
of fields and control sources, but I have fields that need to contain
data
that do not have appropriate control sources - I think it was my own
fault
for not inputting enough when I first created the form. So now I have at
six
fields that are unbound, I have tried linking them to control sources
that
are already linked to another field, but of course that doesnt' work.
Ideally, I would like to add in extra field names (to be renamed by
myself),
that will not have to be controlled by sources that are controlling
another
field. Otherwise it is the text or number is duplicated in both fields.
How can I rectify this problem? I do not understand much of the
terminology
used in access, so in laymen's terms please!!





  #20  
Old August 23rd, 2007, 09:28 AM posted to microsoft.public.access.gettingstarted
Rhianne
external usenet poster
 
Posts: 85
Default Unbound fields

I have created a query, but it does not contain all the areas covered in my
table. Should I rectify this? Thanks.

"James Ivey" wrote:

Hi Rhianne,

I am very new to Access as well.. just a couple of months into it. But I've
gotten lots of great help here in this newsgroup. Here is one piece of
advice I followed (someone please correct me if I'm wrong!):

For my simple membership database I have just one table and one query (at
the moment)

First, create your tables with all the fields you need
Second, create your queries based on your tables.
Third, create your forms based on your queries.

I was told its best to do it that way because it will be easier to maintain
when your database becomes more complex.

Hope that helps,
James



"Rhianne" wrote in message
...
I have added the fields into my table and they are now bound fields.
However,
is it best for me to also create a query as well?

Thanks!

"Rhianne" wrote:

I am new to access and am teaching myself how to create one. I grasp the
idea
of fields and control sources, but I have fields that need to contain
data
that do not have appropriate control sources - I think it was my own
fault
for not inputting enough when I first created the form. So now I have at
six
fields that are unbound, I have tried linking them to control sources
that
are already linked to another field, but of course that doesnt' work.
Ideally, I would like to add in extra field names (to be renamed by
myself),
that will not have to be controlled by sources that are controlling
another
field. Otherwise it is the text or number is duplicated in both fields.
How can I rectify this problem? I do not understand much of the
terminology
used in access, so in laymen's terms please!!





 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 05:53 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.