What if I ...

  • Thread starter Thread starter Dan
  • Start date Start date
D

Dan

What if I want to make changes to a table already in use by forms, queries,
and reports.

Can I copy it to a new name, make the changes delete the old table and
rename it like the old table.

Will the queries still work.

I want to link another table to one of the fields with a limited number of
options, whereas before, the field was simply a text field. Essentially, I
want to make a dropdown box out of the field.
 
comments inline.

Dan said:
What if I want to make changes to a table already in use by forms, queries,
and reports.

Can I copy it to a new name, make the changes delete the old table and
rename it like the old table.

Will the queries still work.
Click to expand...

depends what changes you make. if you delete/rename/change the data type, of
any fields - then relationships, queries, forms and reports may be, all or
any, negatively affected. can you explain *why* you want to create a new
table to replace an existing table? maybe we can suggest alternatives that
won't hold so much potential for disruption.
I want to link another table to one of the fields with a limited number of
options, whereas before, the field was simply a text field. Essentially, I
want to make a dropdown box out of the field.
Click to expand...

no, no, bad idea. first, you shouldn't be entering data directly into
tables - that's what forms are for. second, when data is properly entered
via forms, there is no need for "lookup fields" in tables - thankfully,
because they cause a boatload of headaches elsewhere in a database. for more
information, see http://www.mvps.org/access/lookupfields.htm

hth
 
tina said:
comments inline.



depends what changes you make. if you delete/rename/change the data type,
of
any fields - then relationships, queries, forms and reports may be, all or
any, negatively affected. can you explain *why* you want to create a new
table to replace an existing table? maybe we can suggest alternatives that
won't hold so much potential for disruption.


no, no, bad idea. first, you shouldn't be entering data directly into
tables - that's what forms are for. second, when data is properly entered
via forms, there is no need for "lookup fields" in tables - thankfully,
because they cause a boatload of headaches elsewhere in a database. for
more
information, see http://www.mvps.org/access/lookupfields.htm

hth
Click to expand...
You answered my question, thanks
 
Back
Top