We are getting a 8.3 file error with PrintshopMail 7.2. Unable to open any file that is NOT in the 8.3 file format that is on a network share. If we copy the file locally it can be opened. Also note this is not a Windows issue since ANY other file in ANY other application can be opened from the same network share.
Has anyone seen this before? MS Support and Support for the Synology NAS (file share location) both say it is an application issue. All testing substantiates this.
Thanks
Apologies for the delay in answering.
First question: What operating system is PrintShop Mail 7.2 installed on?
Also, what is the filesystem on that system and on the share drive (ntfs? fat32? etc).
Please note that I can find no issue anywhere in our systems, either development or support, that would indicate that PSM 7.2 has issues with long filenames at all. I just opened S: raining\PrintShop Mail Suite\Design\Templates\Very Simple Business Card2.psmd and was able to open it without a problem.
My OS is Windows 7 x64, we’re on a windows-only network (so probably Win2012 Server R2 for the shares), LDAP authentication, mapped drives for network files. I can only theorize that there’s something different about your network that might cause interference but without knowing what it is, there’s nothing more we can do.
Apologies for the delay in answering…Missed reply.
Windows 7
NTFS (iSCSI via Windows Server 2012r2)
https://www.dropbox.com/s/cax2acn92bqgcsf/Screen%20Shot%202015-10-16%20at%2010.28.59%20AM.png?dl=0
Screenshot of error
Since this issue is non-reproducable on my side (a dbf file named long_dbf_name_test_324523452345.DBF in S:\formation\Ressources\DataFiles opened fine), this is most definitely not something that can be troubleshoot further through these forums.
Simply go here and click “Report an issue online”
I have found a few references to this issue in our internal support system. The problem I’m having though is that every single one of those tickets were closed after lack of updates or feedback from clients (going all the way back to 2006!). One had a potential solution but that was back in 2009 and refered to Windows 98.
Apparently, this is a “known limitation” of both Foxpro DBF and Paradox .db files, I’ve seen this mentionned in just about every reference to DBF and 8.3 filenames while researching this on the Internet. So you’re right that it’s not an Operating System issue. It’s a file type issue, or a database driver issue. Why it works on my PC (and apparently the PC of every technician that was able to get their hands on a client file) and not yours and some other clients is something we have yet to determine.
