Is there a way to add a field to a table, and have the value of that field be a default value, without changing modification date of the records?

After creating the new field, you could modify your ModificationDate field to NOT enter the modified date, save the changes, go do a "replace field contents" script step on your new field to initialize it, then go back and enable the AutoEnter modification date for your ModificationDate field.

That's what I came up with as well. I guess there are no other ways to do it.

Thanks,

Fed

I don't understand. Adding a field to a table does not affect the modification date and time of existing records, afaik. Certainly, if you update the data in a field in the existing records, you change their modification date/time (but that's reality, isn't it?)

Just want to clarify terms here, because beginners read these posts as well.

You are absolutely right, but the question is if you can add a field, and have the default value entered into existing records without the modification date being altered.

Actually, your original post didn't say that you intended to update existing records.

Sorry, you are again right. I did not mention it.

Do you have any ideas that I could use?

the question is if you can add a field, and have the default value entered into existing records without the modification date being altered.

These are two separate issues that have very little in common. Adding a field to a table does not modify any record. Populating the field - or ANY other existing field - with a value is of course a modification of all affected records.

One way to prevent this has already been outlined. I don't know why you're not happy with it; after all, you need to go into Manage Database anyway - so why not disable the auto-enter at the same time, populate the field, then restore the auto-enter.

Another way is to add a calculation field = "Your default value", exit Manage Database, then go back and change the field's type to Text or Number or whatever is appropriate. This too requires going into Manage Database twice - but you save the Replace Field Contents step.