Talked to my VAR today. It is a bug. It’s slated to be fixed in SP 4.0.
One thing that I forgot to mention is that you need to set the Bill of Materials options to “User Specified Name” to reproduce it.
Fortunately or unfortunately I can not still reproduce it.
Do you have the spr for this bug?
thanks.
SPR 1231137
Mike Gera Thanks.
Is it actually the numbers that are causing the issue or is it the number of empty spaces in the file name? That’s something to look at as well.
You also have a special character in your file name. In most larger organizations, the use of special characters are extremely limited- and for good reason. Special character can wreak havoc in a lot of downstream systems. Your ERP system will probably hate them and so will reporting tools!
Ryan
The special character has no affect either way. nor do the spaces. it is definitely the numbers, and that has been confirmed by our VAR.
no clue why, but apparently, Solidworks is aware and is working on it.
Sorry, I got lost in the conversation. What’s the “special character” in reference to?
Thanks.
Mike,
Its in reference to this. the # in our file name.
Thanks.
The thing is Glen (BTW I agree with what you are saying), this new policy would have made some sense in the early days of SolidWorks when there really was a big difference between versions and huge amounts of manpower were used in the new versions.
Now days the new years version is barely different from the last with a few tweaks around the edges (bugs aside). Allegedly this back dating fee was supposed to pay for all the development in the years you missed. If so many people have SolidWorks and are paying subs where is this development?? My guess a lot of it goes to the 3D experience or other projects.
Surely the best way to increase revenue is to improve the product. Make it a product you just have to have. More features, more stuff bundled in for free. Not take stuff away like draftsight.
You’ll never here me say this but, Amen brother! 
They should have stayed the course and listened to the users, not listen to the executives who are now using our annual fees to enjoy their raises and all expenses paid Maldives Luxury Vacations. 
I am certain that once the mirroring bug, and the pack n go bugs are fixed along with many others (hopefully by service pack 5.1), that will be it for us.
we are not benefitting from any of the updates that are worth all of the piñata of broken features we are continually getting.
Insanity: doing the same thing over and over again and expecting different results. (Albert Einstein)
Their very process .. the fact that they even have a schedule for the release of bug fixes tells you that they aren’t sure of their own product … but we still sign up for it every year. no more. not for us. once this years “maintenance” expires .. so does our time for signing up to madness.
also want to throw out a comment about VAR’s. we are always asked to report the bugs to our VAR’s. they confirm the issue, and report it to Solidworks. but I have never received a single email from them informing me of a reported bug for me to watch out for. so … they know of a bug .. but don’t tell their customers about it? and that’s Value Added? for whom are they adding the value? its certainly not us.
just my 2 cents.
“piñata of broken features” 
“we are always asked to report the bugs to our VAR’s. they confirm the issue, and report it to Solidworks.”
Consider yourself lucky, when ever we report a bug the response is, “Proove that it’s reproducable. on your time, and then give us the exact steps to reproduce the issue. Then we’ll involve Solidworks.” Then we go through the same process with Solidworks. Its Dilbert all over again, I don’t know if Scott Adams gets his material from corps like Dassault or if Dassault is implementing what Mr. Adams is writing.
I highly recommend picking up “The Dilbert Principle”, it will so validate your feelings on corporate life.
Has anyone else had trouble with opening 2022 SP2 files with 2022 SP3.1?
She just grinds and grinds and grinds.
Mr Bradford created a new thread about SP4, maybe you could ask him to see if one of your problematic files still displays the problematic behavior..?
https://forum.cadmunity.com/t/sw-2022-sp4-ev-first-thoughts/1830/1
We did have the same issue when going from Sp2 to SP3.1. This also seems to be resolved with SP4 EV.
Makes me feel like I need to comb my hair and straighten my tie. 
image.png
I felt weird calling you directly as Bradford, so I figured I’d add a Mr. 
Makes you take a few years in age upon reading it eh 