Mysterious FileSysObj Behavior
I've developed a medium-sized end-user app. in Access. Most of the code is very run-of-the-mill sort of stuff, but there is one slightly unusual thing against which I am running into some issues. My app provides the capability to load data into a database from a specially formatted plaintext file.
For that function I have a class that does some simple file-system manipulation. This class just has a few simple methods, including a check to see if a particular file is "valid" to load as data for this particular application, and load/save functions.
The application provides the end-user a custom file browser form (i.e., one created wholly by me, not the built-in Windows file open/save). There are a number of reasons I am not using the Windows file open/save dialog, the main one being I wanted absolute real-time control over which files the user can browse to. Only "valid" files show-up as available, to the end user, to load into the application. Also, my attempts originally to use the built-in Windows file open/save dialog were producing some unusual, erratic behavior in some cases.
The app is compiled and distributed as an MDE, and generally works beautifully on Office versions 2000/XP/2003. With some users, however, the plaintext data files are never "found," and simply do not show up as available in my custom file browser. The system behaves normally in every other way, including the ability to use my custom browser to see any drive or folder on the PC. (My custom browser is a facsimile of the built-in open/save dialog which allows the user to browse to any location on their PC).
I've not been able to re-produce the behavior on any of my test-bed PCs, with any version of office or Windows. In fact, I am able to browse to and load files which have proven problematic for other end users.
I can only assume this has to do with some sort of file permission or file properties issue, or some sort of esoteric behavior related to scripting objects generally. Not being a Windows admin. type, though, I cannot isolate exactly what those issues could be. I am in no way educated on the intricacies of scripting objects--I only know how to use them. I can't imagine there is something wrong with my code, though, because it behaves perfectly on some but not other PCs. It is an environment-specific problem. My code is actually quite simple, and engages with the file system in only the most cursory fashion (i.e., getdrive, getfolder, getfile, opentextstream).
Has anyone out there seen any similar or even somewhat relevant behavior? This is a really sticky problem and throwing a huge monkey wrench into an otherwise completely successful project.