There should be an option to tie one CAESAR file's load case editor to another CAESAR file. I.E. not even offer the opportunity to edit it. You can functionally do this as a one-way transfer by importing them.

Benefits:
1. This reduces the burden of checking load cases - you check which master file each CAESAR file is referencing and not all load cases every time.
2. This coerces multiple analysts to model certain things in the same way on a project to save effort.

At my office we have a "standard file" that is used only for load case import which essentially accomplishes the same result.

But I see the value in being able to set up locked down load cases to limit mistakes.

I had this other thought pop in my mind documented here:

http://forums.coade.com/ubbthreads/ubbthreads.php?ubb=showflat&Number=73723#Post73723

But I also realized that more often than not I end up with way more than 9 "simulation" load cases that would need to be married together, so we couldn't just say "take the displacements from another file and plug them into the displacements tab."

It would be my hope that if we could accomplish the "master load case file," we could then go beyond the 9 displacements limit in this very specific case.

FYI I was playing around in Caesar 2019 today and noticed they now have an Import/Export to Excel File.

So I believe you could use a Caesar II file to setup your "master" load cases, export as Excel, save/protect the Excel file.

Granted, this doesn't give you the ability to push changes downstream or lock the load cases in the downstream users.

Still a cool feature to finally have!

I'll have to check it out once I get away from contractural obligations to an older version of CAESAR.

Historically, I'd just copy and paste the data into Excel, and VBA the headers in.

Unfortunately, the more I use Excel to automate my tasks, the more I find that Excel just isn't reliable enough for the tasks I throw at it.