Adding more fields

  • Thread starter Thread starter Mary Hartman
  • Start date Start date
M

Mary Hartman

I have added more fields to a table that I already have a form
designed for. I would like to add those fields to the form but they
don't appear in the list.

How can I add them to the form without having to redo the whole thing?
 
I have added more fields to a table that I already have a form
designed for. I would like to add those fields to the form but they
don't appear in the list.

How can I add them to the form without having to redo the whole thing?
Click to expand...

I have tried a number of ways and keep getting "?NAME" in the control
box when the form is open. It also won't allow me to either remove
that or add anything.
 
Sure. First check and see if your form is based directly on the table, or
(more likely) if it's based on a query. If it's a query, open it in design
view and add the fields. Then you should be able to see them in the field
list.
 
Sure. First check and see if your form is based directly on the table, or
(more likely) if it's based on a query. If it's a query, open it in design
view and add the fields. Then you should be able to see them in the field
list.
Click to expand...


My form is based directly on the table.
 
My form is based directly on the table.
Click to expand...

You should be able to see them then. Only queries can hide them if they are
not in the underlying query. Just a WAG, are the new fields lookup fields?
You should be able to see them, but occasionally you don't see them
correctly.Try expanding the field list and see if they are indeed there.
 
I don't know why i having trouble with this. I am really not this
stupid.

Let me give a step by step what I did, maybe you can find my mistake.

I have a table products. To fill in the table products I have a form
products_input.

When I created the form, I created it directly from the table with the
wizard. I just selected all fields.

Now I have added 6 fields to the table. I am trying to create a
controsl in the form for them.

I insert a text box.

I right clicked on the text box and select properties.

In the data tab, I clicked the" ..."

I click the tables folder to expand it.

I click the table products folder so that all the fields appear in the
center column

I click on the field I want.

Now I have this on the form in design view inside the text box.


=products!products_image_1_text


When I go to regular view, I have this in the box.

#Name?

And it won't do anything. What have I done wrong?

Mary
 
It has no idea what:

=products!products_image_1_text

is. If the name of the field is: products_image_1_text, just select that
from the list in the Control Source drop down on the property sheet.
Alternatively, open the field list and drag the new field to you form.
 
Hi Arvin,

Thank you for keep coming back to me.

These 6 new fields that I added to the table appear neither in the
drop down of the data control on the properties panel, nor do they
appear on the available field list.

Is there maybe a bug that I need a fix for?

I mean besides for myself... bugging you I mean.

That was supposed to be a joke.

Mary
 
if you're using A2000 or newer, did you turn OFF the Name Autocorrect option
when you created your database? if not, suggest you do the following:

create a new, blank database.
immediately turn OFF Name Autocorrect via Tools | Options | General tab on
the menu bar.
compact the database.
import all the objects from your current database into the new database, and
compact it again.

now take a look at the field list in the form's Design view. can you see all
the fields? if not, look at the RecordSource property in the Properties box.
does it show the table name that you expect to see? or does it show a SQL
statement, that starts with "SELECT..."? if the latter, click the Build
(...) button at the right side of the property line, and add the new fields
to the design grid.

hth
 
THANK YOU!!

That did it exactly!!!!!


Mary


if you're using A2000 or newer, did you turn OFF the Name Autocorrect option
when you created your database? if not, suggest you do the following:

create a new, blank database.
immediately turn OFF Name Autocorrect via Tools | Options | General tab on
the menu bar.
compact the database.
import all the objects from your current database into the new database, and
compact it again.

now take a look at the field list in the form's Design view. can you see all
the fields? if not, look at the RecordSource property in the Properties box.
does it show the table name that you expect to see? or does it show a SQL
statement, that starts with "SELECT..."? if the latter, click the Build
(...) button at the right side of the property line, and add the new fields
to the design grid.

hth
Click to expand...
 
So you did have lookup fields. That's what the SQL statement that Tina was
refering to is.

Name Autocorrect does weird things to a database, occasionally corrupting a
form. Tina was right on in suggesting that.
 
So you did have lookup fields. That's what the SQL statement that Tina was
refering to is.
Click to expand...

umm, i wasn't talking about lookup fields, Arvin. i never use the Form
Wizard to create forms, so i'm not familiar with how it might work in
different situations; i thought it might have created a SQL statement for
the form's RecordSource, rather than just assigning the selected table name
to the RecordSource property. if that were the case, new fields in the table
would not show up automatically in the form's Field List - unless the SQL
statement was a simple SELECT * FROM... so i figured if Name Autocorrupt
(yes, i stole that from somebody else here in the ngs, but i can't remember
who posted it <g>) wasn't the culprit, then a SQL statment recordsource was
my next guess. tina :)
 
Hi tina,

I don't use the form wizard either, so I just checked by trying it and it
uses the table or query, not a SQL statement. I do know some of the wizards
do use a SQL statement for things like combo boxes. I'm still guessing
lookup fields, but Name Autocorrect (or better described as Autocorrupt) is
a very likely cause as well. In any case, great detective work. You need to
be an MVP.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
 
In any case, great detective work. You need to be an MVP.

Arvin,
Tina already know that I am going to AMEN that. :-)
 
In any case, great detective work.

thanks, Arvin!
You need to be an MVP.
Click to expand...

well, that's what i wanna be someday when i grow up, guys, but i'm still
just a young whippersnapper... ;)
 
Just because Lynn and Arvin are older than the hills doesn't mean "young
whippersnappers" aren't worthy of the MVP award.
 
Hi Tina,
(yes, i stole that from somebody else here in the ngs, but i can't remember
who posted it <g>)
Click to expand...

I've certainly used that term often enough. It looks like Allen Browne may
have been the first one to use that term, on Sept. 24, 2004, based on a
Google Advanced Search of microsoft.public.access.*:

http://groups.google.com/groups?as_...8&as_maxd=31&as_maxm=12&as_maxy=2004&safe=off

Peiter Linden used it in comp.databases.ms-access the following day,
9/25/2004.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 
Well, tina's Access skills are evident, but perhaps the award should be held
back until that young lady learns to write both little *and* big alphabet
letters! <g>

Cheers!
Fred ("tina for mvp"!) Boer
 
Just because Lynn and Arvin are older than the hills doesn't mean "young
whippersnappers" aren't worthy of the MVP award.
Click to expand...

hey there! Arvin and I resemble that remark. Besides, tina, has all the
non-whippersnapperish characteristics necessary to be an MVP. <g>
 
Back
Top