A family of Microsoft relational database management systems designed for ease of use.
You may well lose data doing this. Normally the lookup field wizard in essence creates a foreign key column of long integer data type which references an autonumber primary key column of a referenced table. Consequently existing values in the current short text column will not be compatible with the data type of the column if its data type is changed, so the data will be lost. To avoid this add a column of long integer data type to the table and update its values to those of the primary key of the referenced table.
Let's assume as a simple example where you have a text column City in a Contacts table. Add a long integer CityID column to the table. Assuming you have a referenced table Cities with an autonumber key CityID and a text column City with distinct value, then execute the following update query:
UPDATE Contacts INNER JOIN Cities
ON Contacts.City = Cities.City
SET ContactsCityID = Cities.CityID;
Once you are satisfied that the table has been correctly updated you can delete the City column from Contacts and create an enforced relationship between Contacts and Cities on CityID.
The CityID column in Contacts will of course show its actual numeric values, and I would recommend you leave it as that, but if you really want to see the referenced city names in the table, change its DisplayControl property to a combo box with a RowSource property of:
SELECT CityID, City FROM Cities ORDER BY City;
a BoundColumn property of 1, a ColumnCount property of 2 and a ColumnWidths property of 0.
If the referenced table's key were a 'natural' key, i.e. the City text column in the above example it would be possible to use the lookup field wizard without losing data, but this would not change its data type; it would merely change its DisplayControl property to a combo box.