Can I lock files so V8i can only open them, while only CONNECT can open others?

Back in 2018, we primarily switched over to CONNECT.  Recreated all linestyles, levels, etc. to give ourselves a correct clean slate.  However, every project before 2018 still uses all the V8i fonts, linestyles, etc.

Is there a way to lock all files before 2018 to only open with V8i, while only allowing all 2018 and newer files to open in CONNECT?  All users still have both versions because we still both, but I only want the older jobs to pull the older data.  Any help would be great.  Thanks.

Parents
  • I recreated everything because over the years numerous linestyles and such had been created with different sizes, spacing, etc. I found it easier to just create the items we needed correctly rather than go through numerous resources files and try to only keep what we needed. This way all linestyles are placed at 1 scale, old fonts don't even show up in CONNECT, and numerous other things that help maintain much better looking plans.

    As far as configurations, yes V8i and CONNECT each have their own separate setups.  I did add the CONNECT resource files back into the V8i setup so even if all work is done in CONNECT, but someone opens the file in V8i, they still get the correct look.  Since I didn't add V8i into the CONNECT setup, it's easy to see the linestyles and fonts that are incorrect since they will not show up as we need them too.  I did that in hopes that it forces more people to use the newer CONNECT version.  I don't want our work coming to a halt when V8i support is dropped.

    All our projects are on the same network drive.  They are separated out by the year 2016, 2017, 2018, 2019... I was hoping it would be easy enough for people to only use V8i prior to 2018, and everything from 2018 onward would be intended as CONNECT projects.  Since people can't do that properly, I was looking for a way to "lock" the folder structure to a certain version of MicroStation.

    Thanks for the help though. I'll continue to remind everyone until V8i is no more.

  • V8i SS10 and CONNECT both have option to set project ID for each DGN file so you could set that each use different project name but it won't lock it to specific version just will show warning of project mismatch.

    Another option would be to rename extension for files from DGN to DXN or similar and set that DXN is opened only by CONNECT.

    Do you still use RSC and not embed them in DGNLIB?

Reply
  • V8i SS10 and CONNECT both have option to set project ID for each DGN file so you could set that each use different project name but it won't lock it to specific version just will show warning of project mismatch.

    Another option would be to rename extension for files from DGN to DXN or similar and set that DXN is opened only by CONNECT.

    Do you still use RSC and not embed them in DGNLIB?

Children
No Data