Simply because I have a healthy fear of "Replace Field Contents", I would write a simple loop script
SetField (Field2 ; Field 1)
SetField (Field 1 ; "" )
Next (exit after last)
Hit run and go to lunch. It shouldn't take very long anyway...
You can buff it out with safeties like
SetField (Field 2 ; If ( not IsEmpty(Field1) ; Field1)
SetField (Field 1 ; If ( not IsEmpty(Field2) ; "")
just to check to make sure the data moved...
I am not a developer, but is the script in its entirety (other than me renaming the fields)? If so, I'll revise, make a DB backup, and give it a shot.
Any other suggestions or tips before I do this?
Thanks very much.
Yup...pretty simple stuff.
Backups are good...and use the Script manager to make the script so you get all the syntax right...
In your 100k found set, put the cursor in Field2. Then go to Records > Replace Field Contents > Replace With Calculated Result. Specify Field1 as the calculated result. Then hit Replace.
Allen and smith are right on...
As long as you're making a backup, do it that way.
I tend to script little shifts like 100K records just cause I'm uber-cautious. (read "afraid of Find/Replace)
It is really the best way to go.
When I looked at your post I thought along similar lines as Eric. Note, however, that that is really just the action part of such a script. Before the loop you need to establish context with steps that do the following:
1. Go to a suitable layout
2. Perform a find to isolate the 100k records in which you need to make this switch
3. Go to the first record
Then you can run the loop, which is essentially moving the data from field 1 to field 2. If that is exactly what you want to do in every record in the found set, then go ahead. If there are any provisos to take into account you would need to address those first. One that comes to mind is: do any records already contain data in field 2? If so, do you want to keep it and add field 1 contents to it, or replace it with the field 1 contents?
Thanks guys for the multiple suggestions. I'll try the Find/Replace and see if that works as intended.
To clear it up, there is no existing data in Field2.