How can we help you today?
Why aren’t some file types suitable to open via MyWorkDrive?
Why can’t I open certain file types (such as Databases, PSTs, Accounting systems and the like) work via MyWorkDrive?
A number of file types are not well suited to remote access programs like MyWorkDrive or VPN because their connection methods were designed for always on local access, or at most SMB protocal on a LAN. They were not designed for slow, high latency connections such as the Internet or VPN, and were not designed to be converted/transmitted via HTTPS the way MyWorkDrive does (pulling from the sever on demand; not storing files locally in anticipation of access), nor being subjected to the types of packet inspection HTTPS is subjected to by firewalls, WAFs and endpoint security.
The average home internet bandwidth in the US is approx 100mb/s of download and 20mb/s of upload, not accounting for ping time latency and vulnerability scans at each hop. Where as the typical office lan is 1000mb/s each direction – with no hops and minimal scanning. Programs designed to expect an immediate response with very short timeouts will not function well with long waits, deep scans and packet interruptions when only given 1/10th their expected connection, at best.
Files like Databases, large media files, design files and the like should be accessed via the author’s approved networking methods or via a Remote Desktop session – not via MyWorkDrive. Our default block list (when optionally enabled) specifically includes Quickbooks, Access, and PST files for exactly that reason.
Some applications to specifically avoid opening over MyWorkDrive include:
Photoshop / Adobe Creative
Legacy Sharing in Excel (Shared Workbooks)
(not to be confused with co-editing via Office365, which is fully supported in the Web client, iOS/Android and Windows Client)
In general, if it is a multi-user database product, or a product that uses a large number of reference files, the files should not be stored on a Share in MyWorkDrive and opened remotely by clients. Please refer to the original software author for networking best practices for the product.