InfoPath Dev

I published a form on our shared drive that employees use to capture client info. Employees then save these forms on the same shared drive (but in a different location) so that the entire unit has access to all client info. All has worked flawlessly until recently when a single employee lost access to all versions of the form, template and saved. Error message is something like "cannot access file because of incorrect filename or pathname." Funny thing is everyone else can still access all of her files on the shared drive. My fear is that this could happen with other users and that we could lose access to our client information. Please help!

I don't have a solution that is particularly solve your form opening issue, but I do have a solution that would help ensure no loss data.  You should have all your forms setup to save all the content in a sql server database or another global database that way it would ensure that no data is lost.  The data can then be made usefull with other applications than just in the infopath forms.  Also form data is saved in xml format that has special tags to associate it with infopath, so you still no matter what have that data.

Also are you getting the error when using infopath to open the form or how are you opening the form?  If opening in office it might have been due to an update of office.  In office 2007 there is a diagnostic tool you can use and I have found it to solve most little common errors.

You have stated the best practice Barmatt

What I have seen before is that the map drive or UNC is different so that they are accessing it in a matter differently than it was published.

When the Form is created it checks that the client is accessing it at the published location and XML files check this to.

So if everyone use \\server\share as it was published and this user setup x:\ as a map drive it would break. Or could be visa versa.

Hope that helps.

 if shared drives are the only way for your environment to work with, then by all means i hope your company is using a DFS structure.

without DFS, your users will scream at you when the server goes down.

with DFS, is one of the DFS hostings  servers is down for maintenance, other will pick up the redirections

not 100% foolproof, but still better than mapped drives or UNC as Clay pointed out.

 Besides, can the user having the issue still put anything else in these folders? maybe it's an ACL permission on the fileserver itself?