I have a database that is used as a template to clone new databases from as needed. Each new database must start out containing no records, so that any records that are added to it belong only to that database.

The problem is with a repeating field. The field is simple enough - 14 repetitions containing consecutive numbers incremented by 10 starting with 20 and ending with 150, and stored globally. I can enter the values in a cloned database with no records and each added record retains all 14 values. I can make a copy of the original file and the values are retained. I can delete all records in the database and the values are retained.

But, if I Save a Copy As > a clone (no records), the repeating field comes up empty in the the clone. Since cloning an existing database is our usual method of creating a new database to work with, this requires re-entering the values in the repeating field every time. If that isn't done, then the question arises as to why none of the calculations that make use of this repeating field are working.

I have found a few ways to get the values to automatically appear in the repeating field - including Value Lists and Auto-Enter options, but each method ended up with every value listed in the first repetition. This, of course, is not acceptable.

Is there any way to retain the values in each of the repetitions of a repeating field, even after the database is saved as a clone?

Thank you.

The field is simple enough - 14 repetitions containing consecutive numbers incremented by 10 starting with 20 and ending with 150, and stored globally.

What is the purpose of this repeating field?

It is used to show dollar amounts from $10 to $150 in $10 increments, which are displayed along with calculations that apply to each value. Every record in the database uses these same values, so I made it a permanent repeating field. In a similar database, there is always at least one record present, so making the repeating field global keeps the repetitions populated. Not so with this database template, where I start with a zero record clone.

If it's for display only, you could type the values directly onto the layout...

Or you could use a repeating calculation field and make it either unstored or global.