yes, you can set up a relationship that uses the job number as a match field and auto-enter field options to copy data via that relationship.
If you need more help with this, you'll need to describe your data model in more detail.
To be clear, I just want to copy the data, not have an ongoing relationship between records. If any of them change, I don't want them to affect each other.
I'm happy to provide more detail. This sort of thing is just beyond my skill set. I added a screen shot to the original post of one of the sections of fields. Each record is assigned a serial "Job Number" which is used throughout the company to track job details. My notes from a call with my client are in red. There are currently five sections like this per record.
What additional info can I provide?
The same relationship that you would use to link to data dynamically can be used with auto- enter field options to copy data into fields and this data will not change if data in the related record is later modified.
As I stated already, you need to document your data model. You need to describe the fields, tables and relationships that store the data you want to lookup.
Here's a Database Design Report
All the fields are in single table named "Danger_jobs". It's labeled in purple under Relationships > Table Occurrences
All fields and needed changes are in the Manager layout.
What else can I show you?
Not a DDR. How about a screen shot of Manage Database Relationships?
But only one table seems very problematic. One normally need multiple tables linked in relationships to get full functionality out of a relational database system such as FileMaker. That "copy data from a hundred fields" is a possible sign that you have set up multiple fields where you really need multiple records in a related table.
But here's a link to the basic method where entering data into a match field can trigger a "look up" from a related record with matching data in its match field. The two Tutorial: What are Table Occurrences? that make up the relationship can even be occurrences of the same table:
Thanks for the link, I'll look over it.
Are you copying data from one record of Danger_Jobs into a new record of Danger_Jobs?
Yes. If it's possible.
Will "previous job number" be the value of Danger_Jobs::_fk_QuoteNumber? Or is this the value of another field? Does it uniquely identify records in Danger_Jobs?
Another field. Field name is "Job#"
Yes, it does uniquely identify individual records in Danger_Jobs.
Define a new field in Danger_Jobs: SelectedJob#. You may find it useful to define this as a global field. Then create another Tutorial: What are Table Occurrences? of Danger_Jobs and add it to you relationship graph to produce this relationship:
Danger_Jobs::SelectedJob# = Danger_Jobs 2::Job#
Then you can click on the field tab, Select the Danger_Jobs table and double click various fields to open the Field Options dialog. From there you can select either Looked up value or calculation on the auto-enter tab to select the same field from Danger_Jobs 2 and then selecting or entering a Job# in SelectedJob# will cause that field to lookup (copy) data from the same field of the selected record.