Changes in Datasheet not in form

R

Rock

Hello,

In Access 2002 in Datasheet mode I have changed a couple of normal text
fields into Lists fields with me inputting the data (not from another
table).

The List fields I did before I created the form are fine, but how do I
update the form to reflect the new changes to the other fields.

Thanks

Rock
 
J

John Vinson

Hello,

In Access 2002 in Datasheet mode I have changed a couple of normal text
fields into Lists fields with me inputting the data (not from another
table).

The List fields I did before I created the form are fine, but how do I
update the form to reflect the new changes to the other fields.
Click to expand...

You've been misled by Microsoft's "lookup" misfeature.

There is no such thing as a "lists field". The fields in your table
contain DATA - just one value per field - in Number, Text, DateTime,
etc. datatypes.

A listbox, or combo box, is NOT DATA - it's a display tool. The fact
that you can use the Lookup Wizard to "insert" a listbox into a Table
Datasheet merely *conceals* the fact that what is actually stored in
the table is (usually) a Long Integer key, a link to the lookup table.

You can put a Listbox or a Combo Box on a form bound to this field; it
makes very little or no difference whether the Table Datasheet
contains a textbox, a listbox, or a combo box. Just open the Form in
design view and select the control; right click it; and select Change
To if you wish to go from a textbox to a listbox or vice versa.

John W. Vinson[MVP]
 
R

Rock

John said:
You've been misled by Microsoft's "lookup" misfeature.

There is no such thing as a "lists field". The fields in your table
contain DATA - just one value per field - in Number, Text, DateTime,
etc. datatypes.

A listbox, or combo box, is NOT DATA - it's a display tool. The fact
that you can use the Lookup Wizard to "insert" a listbox into a Table
Datasheet merely *conceals* the fact that what is actually stored in
the table is (usually) a Long Integer key, a link to the lookup table.

You can put a Listbox or a Combo Box on a form bound to this field; it
makes very little or no difference whether the Table Datasheet
contains a textbox, a listbox, or a combo box. Just open the Form in
design view and select the control; right click it; and select Change
To if you wish to go from a textbox to a listbox or vice versa.

John W. Vinson[MVP]
Click to expand...


Thanks John,

You made it very clear now about them NOT being data, but just a
cosmetic List' to save typing.

Actually I meant 'Combo boxes' not 'Lists', sorry..

However I did the changes in the Form as you suggested.

Does this mean I would be better off to change the Table boxes back to
just a text box rather than keep them as Combo 'Lists' ?

As I guide myself thru this exciting maize I have a couple of other q's,
but will keep them as other posts.

Thanks again,

Rock
 
J

John Vinson

Does this mean I would be better off to change the Table boxes back to
just a text box rather than keep them as Combo 'Lists' ?
Click to expand...

I'd be inclined to do so, but if you are fully aware of the actual
structure of the data and of the limitations of the lookup feature
(again, see http://www.mvps.org/access/lookupfields.htm for the
limitations and problems) you may not need to.

If (as is proper) you never use table datasheets for user interaction,
it may not matter much at all, you won't see the textboxes or combo
boxes in any case!

John W. Vinson[MVP]
 
V

Vaibhav Joshi

Rock..... to cut matter short and simplyfy you need do this. Go to the form
that you want the latest change reflected. Rename the original field that is
still a Text Box(The Name Property by adding a 1 or xx kind of suffix). Also
remember to move it to some other place on the form that is not very
important. (Only temporarily) Now drag and drop the Changed Field on the form
again directly as if you are doing it for the first time. Now this newly
dropped field will automatically now inherit the properties that have been
set in the Background Table itself. Once you are sure and comfrotable with
the changes that you have made.... delete the original renamed field. In case
you have put some VBA Programe code behind the original field the dropping of
the same field from the field list should auto relink it with the new field
as the original Field name being absent will also take the same name as that
of the Field.

That should work for you.......
 
Top