I have been brought into an organization to rework an existing database that tracks freezers and other controlled environment units at a university. One of the primary issues has been to change the identifier for each record from a location-dependent string to a unique numeric identifier for each freezer. I need to create a new field in the primary table (rather than alter the existing ID field), link it to new fields in the secondary tables that have relationships dependent on that unique UnitID (without deleting or altering the existing identifier field), automatically generate new ID numbers in the primary table and have them automatically populate out to the corresponding fields in the secondary tables. Is this possible? I tried doing it by creating a new field in the primary table called UnitID set to Auto Number, then created like-named fields in other tables and establishing a one-to-one or one-to-many relationship (depending on the conditions), but the UnitID numbers, of course, didn't show up in the new fields in the secondary tables. I tried redoing the creation but not setting the UnitID to AutoNumber, created the relationships and then tried to change the UnitID field in the primary table to Auto Number, but again, of course, you can't change the field without breaking the relationship. With over 400 records in the database so far, and 500 more to come shortly, I'd prefer not to have to do this manually. I'm not adverse to using VB to write a script, but have MINIMAL experience with VB. Is there a relatively simple solution out there?