Filemaker Import XML Data
Save the current database (never make major changes to the only copy that is being used)
Backup copies throughout the process. Make notes of the process.
Working on the COPY, optionally, Save As Smaller (this compresses or optimizes the database)
Importing the XML data can be confusing due to field name mismatches.
Opening the XML data as a new database can allow renaming Field names, making import simpler.
Creating a Calculation Field to save the old address will not work
Using a Set Field script step would be best.
HI David, thank you for your reply. I see you're in Seattle, so are we.
Creating our own script to move the old address to a different field before importing the new information is a bit beyond our capability. We are a non-profit who rely on volunteers for a lot fo this stuff. Do you know of any way we can hire FileMaker to do what we need? I would ask them directly but it seems we would have to pay for the phone call, which we will do only if necessary. Any advice is much appreciated.
"Do you know of any way we can hire FileMaker to do what we need?"
I seriously doubt that's something Filemaker can do for you, but maybe there's a local filemaker consultant who might be willing to donate their services on this for you...
I have done work for non-profits through formerly OneNorthWest.
I found non-profits similar to disfunctional families, no offense.
I would suggest contacting OneNW. New name escapes my memory.