Hi,
>>"I'm trying to understand, why it would matter so much to a workflow, to know if there's a new DWG version. That's off the track?"
No.
>>" Or does he just want plenty of time to budget for a possible software upgrade? If so, why not just say that?
I don't know, I am not the one.. I think he have the answer he was after and leaved the place.
@strangby Come on, tell us more (please), so we can see more clear.
honkin: >>"So I'm quite curious, how someone would have an issue with a new version."
It starts with running projects, for running projects it is very usual to get trouble if you are using Versions with different native DWG versions, so have have to plan.
But TO has some plugIns, 3rd. party and own programmed software...
Your last answer sounds you are knowing enough to know what can be a reason in theorie, like:
Have to plan budget, have to order, have to test.... or you have to test and edit your own programs.
Think about a program what is reading the dwgversion from the files to list them as additional column,
or to fill a database with such tools and and and.
you need to update such a program. 100 other ideas why it could be important.
----
Note, my "Off track" was directed to the reply-part what is Editited by moderation now
and because of the fact that there a a lot of reasons why it is important (and why saveas in older DWG version isn't a solution.
But your first reply was to Rob, that's the first and main mistake 🤣
your second fail was commented by Rob: BTW, a simple save as to ...Your analysis is flawed
and he is right. Saveas in older version can be the biggest fail in some situations,
also a simple open&save in the newer version.