So digging further i have found why some things work and not others, and it is a difference in behavior between the full client and Web Access and the error message comes from Web Access but it refers to a Windows API Function that's failing (NormalizePath). The full client when opening an office doc will save the temporary file to C:\Users\UserName\AppData\Local\Temp\#\Docname Truncated to 74 Chars_EntryID\TruncatedDocName
So it looks like the full client has a built in function to truncate the temporary file name when it's longer that 74 characters.
Web Access stores an office document in 2 different places depending on whether you choose "View" or "Edit". We noticed a difference in behavior between the two options only because the docname was slightly above the characters limit. When choosing "View" it stores it in
C:\Users\UserName\AppData\Local\Temp\#\SomeGUID\Docname
When Edit is chosen it stores it under
C:\Users\UserName\Documents\My Laserfiche Documents\Docname\Docname
And webaccess to does not auto truncate the path or filename if it's longer than 74 characters as the Windows Client Does and the windows function NormalizePath that the office integration uses seems to be limited in the size the path can be.
So now i understand what's happening a little better, can this be filed as a Bug for the Web Client? If Laserfiche allows document names of 255 characters, i would imagine there shouldn't be any scenario's where a user can't access an electronic file because the name is somewhere close to that. Any thoughts on this? I understand we can't change the windows function, but it seems the fix has already been built into the Windows Client, can it get added to the Web Client?