Changing Data Type

  • Thread starter Thread starter emjava
  • Start date Start date
E

emjava

I would like to change the data type of some fields (that contain data) from
"text" to "lookup." If I'm entering the same data/values in the lookup that
are currently in the text field, will I have to re-enter that information?
(I only have 49 records currently.) What's the worst thing that can happen?

Thank you!
 
Em,

You would have to re-enter the data because your field will become
different. You will probably choose a dropdown list which uses a number as
keyfield. The entries in the tables which contain text will be deleted and
you have to re-enter those. Furthermore Access will create a relationship for
the lookup if it doesn't exist. As you stated nothing crucial for 49 records
but you do have to think about the consequenses when changing in design
afterwards.
 
Maurice--

Yes, thought so. This is my "test" database that I'm learning on, as I go.
I know it's wrong wrong wrong to change these things after they have been
created. And actually, I first used a combo box and want to change it to a
lookup. I don't mind re-entering.

Thanks for your prompt response!
 
I would suggest you not use lookup fields. They really are a problem to deal
with and will cause problems other places in your applications.

What is it you want to accomplish? Perhaps we can offer a better solution.
 
That's something I'm wondering about as well--when does one use a lookup vs a
combo box vs a list box? Basically, I have one table--very simple--and I
want to use a drop down box for easy entering. I'm learning Access, but have
some (old) FileMaker pro experience.

Thank you for your help.
 
You can use a combo box (drop down) for searching without a lookup field.
How you do it depends on what you want to do. Tell me what you want, and I
will provide and example.

Combo boxes are very useful for searching for specific records, filtering
your form or report, or for entering standard, fixed values in a field. When
used as a search or filtering control, a combo should be an unbound control.
When used to enter standared fixed values, you would use a bound combo box.

List Box controls are useful when you want to present a number of rows on
your form that are there for information and selection or when you want more
than one column visible at all times. List Boxes are also very useful if you
need to allow a user to make multiple selections.

As to Lookups, don't use them at all. What you see visually in the field is
not the actual value in the field, but a value that is a reference to a
lookup table that represents the value in the field. These can be very
confusing and are hard to use in queries.
 
Good to know! No more lookups for me. I'll stick with my combo box.

Again, thank you for your help!
 
You would have to re-enter the data because your field will become
different.
Click to expand...

Ummm...

No.

Changing the Lookup property of a table field from Lookup to Textbox will
remove the lookup from the table, but the table will still contain the numeric
foreign key, and the Lookup Table will still exist. You can easily use the
same data in the two tables on a Form, using the lookup table as the rowsource
of a combo box on the form, and retaining the same data in the main table.
When viewed in table datasheet view you'll see numbers because *that is what
is actually in the table*; no data will be lost, nothing need be reentered and
no damage will be done.
 
Correct but in this case the question was the other way around so from text
to lookup and in that case the data (depending on the data entered) will be
deleted.
 
Back
Top