0 Members and 1 Guest are viewing this topic.
Yes as Darren Said. This is not the cause of the problem, but it is a bad idea to have 2 separate version's pointing to same shared database, I was told that by Andy awhile ago. I'm not sure what issue's it can or could cause but when the lead programmer Tell's me something, I don't question it! lolMy setup is a little over the top but I have the Autodesk Fabrication Main Folder. I Than Break down by Year/Version than By a particular "Database" Some are exactly as previous year but are run by the said years CADduct. No I don't have all the Versions Loaded The older version 2020 back are Backed up now. But wanted to give you and others an idea.
Kinda makes sense seeing they dont have write permissions sort of. Still playing with fire you might get a burn. lol
I've been managing the database in ESTmep 2020 and our estimating department was using 2018.
Quote from: cnash link=topic=16759.msg110204#msg110204 date=1618919514[quoteI've been managing the database in ESTmep 2020 and our estimating department was using 2018.Do you guys like using ESTmep with CAMduct and CADmep? We've always kinda flirted with the idea of moving that direction with the estimating software. Never pulled the trigger. I'm sure the transition is relatively smooth.
From what I have understood (I could be mistaken) is that users with admin permissions should stick to one version and not go backwards, once going to a later version stay there. But other standard users can use the same database in multiple versions without issue.
Quote from: cnash on Apr 19, 2021, 13:19:00 PMFrom what I have understood (I could be mistaken) is that users with admin permissions should stick to one version and not go backwards, once going to a later version stay there. But other standard users can use the same database in multiple versions without issue.Didn't think about this, but you are correct. I was testing everything I modify in 2020 in 2018 as well just to make sure there were no issues. Thankfully nothing has come up over the time I have been doing it this way.Generally speaking you're right but there are exceptions. Adding a new CID to a service then using that service in a version that doesn't support it is one of the most common examples. But there are others. Luckily (or not) Autodesk doesn't add CID's often. The newer hanger patterns were one of the last examples in this area.But this holds true for other things too....reports that access fields that didn't exist in prior versions, etc. Those things will not work as expected even with no read-write in older versions.
Do you guys like using ESTmep with CAMduct and CADmep? We've always kinda flirted with the idea of moving that direction with the estimating software. Never pulled the trigger. I'm sure the transition is relatively smooth.