Scott, we are chasing this error and other similar ones on a WinNT network. In our case, we found the error 2005 was occurring when a form could not be opened by the NETWORK, not by VFP (thus the intermittent problems). We trapped for it in a loop, which puts up a WaitWindow, waits 3 sec. (to allow network traffic to adjust) and tries again. For 100 tries unless the user presses < ESC > which exits the form. We hit it about 15-20 times per day, but rarely go more than 3 tries.
In our app, the code was added to the Visual MaxFrame DoForms() code.
If you're having this problem, are you having similar network problems like a form loading, but not all the DBFs loading? Or a CDX file not loading? Again, this happens irregularly but always during network-busy times.
HTH
Barbara
>Greetings!
>
>Our development team is experiencing ERROR 2005 intermittently.
>The following example illustrates a common occurence:
>
>When running a form or formset, the following message is displayed;
>
>"Error loading file - record number 12. OurFormName
>members>.Parent : File Access is Denied"
>
>The following is displyed when help is clicked from the error message's dialog box;
>
>"You have attempted to set a property to an illegal value through the language."
>
>The forms/formsets in our project(s) are created without wizards and our client/server methodology mixes various data environment scenarios dependent upon need. Simply put, any given form or formset, regardless of its complexity, inevitably generates ERROR 2005 one time or another, but only in the IDE.
>
>Things we have tried to rectify this error:
>
>The error cannot be traced to illegal property assignment. All .SCA files have been carefully scrutinized and present no evidence to the contrary.
>
>The form/formset and all inherent files (data, .scr, etc) have attributes of archive (nothing read-only).
>
>Tracing through the very ambiguous "record number ##" via tab stop, object order (by when-added-to-form, by manual index, or by .SCA order, has been in vain (no illegal values or assignments). We wonder which "record ##" Fox is referring to, which led us to...
>
>Scrutinizing the base tables, the respective data environments, and thier properties. No corruption or illegal assignments found.
>
>At a loss, our team has had limited success by closing all tables from the command window prior to running the form/formset. This works 50% of the time. (?)
>
>Closing VFP 5.0 and restarting. (fingers crossed)
>
>Cold/Warm boots to no avail. We already sifted through the UserGroups, Microsoft, Newsgroups, et al, and found the articles on the various report/label memory leaks, but we cannot see how this affects running forms in the IDE.
>
>Our team appreciates any thoughts you may have to offer concerning such a well documented error <g>. Thanks, Microsoft...
>
>Sincerely,
>- Scott
