And how would I do that? I mean sure, I know what should be open and, AFAIK, all the tables are open. I'm not doing any low-level file work in that form, so it's not something like that. It doesn't tell me what file (I've never understood VFPs inability to include the file name in certain error messages when it can't find a file it is looking for - one example is "API library not found" - why can't it tell me which API library?). In other words, it's not my code looking for a file that causes the problem and I don't know what file VFP is looking for and it won't tell me, so how do I test? This is a bit like proving a negative. Anyway, I'm thinking this may be a false error message.
The temp and resource files are pointed to the user's temp folder (i.e. the app is profile-aware and has to be to run properly under Terminal Services).
>To help narrow down the error can you test to see what file is not open.
>Is it a VFP DB or SQL DB.
>How have you setup temp & and resource files for each user.
>
>>I'm not sure how intellisense would play into this, but maybe you can provide me with more details on what you're suggesting and I can check it out.
>>
>>>JAG Is it a rights issue with intellisense.
>>>
>>>>After installing a new version of a program for a client, two or three users are getting a strange error (1113 - File is not open) that supposedly happens in the MouseWheel method (although I have no code in that method).
>>>>
>>>>I get this reported as the method: frmcustinfonew1.pgfcustinfo.page3.pgfnotes.page1.edtnotes.MouseWheel
>>>>
>>>>I'm thinking this is a false error message, but it does seem to occur when the user is scrolling in an editbox on page 1 of the pgfNotes pageframe. I have asked the user how she is actually effecting the scrolling - mouse wheel, clicking or dragging in the vertical scroll bars, using the down arrows, telekinetics, etc. - but have not gotten her response, yet. There is a grid just above and I'm wondering if she might be scrolling there, but the error message points at the editbox (if I can trust that error message - this one is a bit flakey).
>>>>
>>>>This is on Terminal Services and it does seem to be limited to just a few people, so I am wondering about the mouse drivers. I am going to suggest to the client that they change out the mice and the drivers, but that's about all I have to suggest at the moment because I am not able to recreate it (on my local machine or while running it via Terminal Services).
>>>>
>>>>Any suggestions would be appreciated.
>>>>
>>>>Russell Campbell
