I am getting the following run time error 3042 - Out of MS-DOS file handles. Can anyone give me any suggestions or point me in the right direction? I have searched the Microsoft site and few others but to no avail. Thanks in advance.
3042 Run Time Error
- Thread starter LynnaM
- Start date
- Local time
- Today, 06:36
- Joined
- Feb 28, 2001
- Messages
- 30,474
What version of Access are you running and are you running some VBA code that opens files underneath a form or macro?
The business about not enough file handles indicates to me that something is opening files and not closing them. If the files were closed, you could recycle the file handles...
If this is an old enough version of Access, you also would run into the problem of having to get into the file C:\CONFIG.SYS to reset the FILES= statement to have a larger number. But that would imply like, version 2.0 of Access under Windows 3.1 or so.
The business about not enough file handles indicates to me that something is opening files and not closing them. If the files were closed, you could recycle the file handles...
If this is an old enough version of Access, you also would run into the problem of having to get into the file C:\CONFIG.SYS to reset the FILES= statement to have a larger number. But that would imply like, version 2.0 of Access under Windows 3.1 or so.
I am using Access 2000 so that eliminates one of the possibilities.
I will try to to explain this w/o boring you to tears. This database is on a network. When the users at our plant use the database there are no problems but the user that receives the error is located at another plant. That user has a button on a form that opens a Word document and that is when he gets the error. Access is running in the background, it does not close while the user views the Word document.
I hope that helps a little with the clarification.
I will try to to explain this w/o boring you to tears. This database is on a network. When the users at our plant use the database there are no problems but the user that receives the error is located at another plant. That user has a button on a form that opens a Word document and that is when he gets the error. Access is running in the background, it does not close while the user views the Word document.
I hope that helps a little with the clarification.
