Use the Same Version of software to Admin your Database
Consistently use the same version of software for all administration work. You can draw/model/estimate/etc using any version. Just make sure your users don’t have administrative permissions on their login. But for administering your database, always use the same version. Here’s why…
You can work in multiple versions of CADmep, ESTmep, CAMduct and even Revit (w/Fabrication Parts) using the same database configuration. In other words, the configuration itself is “Version Agnostic“.
For Revit Fabrication Parts, database compatibility starts with version 2016. The other Fabrication products like CADmep, ESTmep and CAMduct, compatibility goes back to at least the version prior to 2013, before Autodesk acquired the software.
What’s the problem?
You often get new functionality in newer versions of software. Versions of the software that require new data, automatically adds the new data to the database tables. When you only Use older versions of the software without administrative permissions, it ignores that extra data when it encounters it. This is why old versions work with configurations edited with newer versions,
When you try to use an older version to Administer your database, it rewrites those tables but doesn’t see the added data so it gets overwritten. This is why you should stick to the same version when editing your database.
You do not have to use the latest version to maintain your database. You can continue to use an older version for administration. Just don’t use a newer version then go back to the old. You’re perfectly fine to stick with an older version. You just won’t be able to take advantage of new features that rely on added data the new version offers. When you are ready to start using a newer version for Administration, you can make that change anytime but you should also stop using the older versions for administration.
Let’s Demonstrate the Issue
You can watch the video at the end of this article to see an example. In 2019 Autodesk added a new Connector setting for “Connector Matching”. We won’t go into what this does here but you can see in the following image the difference in the right-click menu of connectors.
When you watch the video, you’ll see me switch between 2 different versions of ESTmep. I could use any product but ESTmep lets me quickly open and close a database so I can move between versions quickly.
If you look at the configuration icons, you can see which version of software is being used. ESTmep 2019 has all BLUE icons. You can see ESTmep 2018 uses RED icons except the one BLUE 2019 configuration.
The video starts with “A Test Config” loaded in ESTmep 2019. I select one of the Connectors and change its ‘Connector Matching‘ value. Next, I exit and go back into the same configuration again in 2019 to show the value remains the same. At this point, everything is working as planned.
After exiting the database in 2019, I then switch to ESTmep 2018 and load the same “A Test Config” database. I make a copy of a completely different connector. This is where the problem starts. ESTmep 2018 has no knowledge of this ‘Connector Matching‘ data. Your “Connector Matching” data is over written as soon as ESTmep writes the Connector tables using the format it knows.
Finally, I go back into ESTmep 2019 and verify the data is gone. The default value for the Grooved Coupling’s “Connector Matching” data changes back to “Same“.
You can see for yourself by watching this video.