The only thing you can do is use Review Assembly and see the passes, but even in Review mode you can't edit it there because it needs a connection to the database where the assemblies live.

So I understand, it seems if the assemblies the other estimators used are also included in your copy of the database, they should be available for editing when you restore to your environment and connect to your copy of the database. If the other estimators are using assemblies that aren't included in your copy of the database, the problem you're having makes sense.

If the issue is being driven only because of the WBS codes (not sure that this alone would cause the problem if the assemblies are the same across all database copies), try exporting your WBS lists to Excel so the other estimators can import them. This is easier than sending a copy of the database around.

Collaboration across offices is best supported using a shared SQL Server instance but you probably already know that.

The only thing you can do is use Review Assembly and see the passes, but even in Review mode you can't edit it there because it needs a connection to the database where the assemblies live.

So I understand, it seems if the assemblies the other estimators used are also included in your copy of the database, they should be available for editing when you restore to your environment and connect to your copy of the database. If the other estimators are using assemblies that aren't included in your copy of the database, the problem you're having makes sense.

If the issue is being driven only because of the WBS codes (not sure that this alone would cause the problem if the assemblies are the same across all database copies), try exporting your WBS lists to Excel so the other estimators can import them. This is easier than sending a copy of the database around.

Collaboration across offices is best supported using a shared SQL Server instance but you probably already know that.