Reverse Phone Search

Find out the owner of any cell phone or unlisted number. Results include name, address, and other available information. Your search is 100% confidential.

domain lookup api

Run time errors commonly plague old and new Windows systems alike. In Windows 95, the “Open for binary” command will fail if the control is set to share level access. When this occurs, you are typically presented with the error message: Runtime error 75: Path/File access error. Runtime error 75 is just one of many that are bound to pop up from time to time. This article will discuss what is behind this error and it will offer solutions.

What Causes Runtime Error 75?

The run time error mentioned above is one you will only encounter on a computer running Windows 95. To fix this error, we recommend using one of the following methods:

• On the shared resource, change the access permission from read-only to full control.
• If Windows 95 is running in a Windows NT domain, switch to user-level access.
• Use Win32 API calls to access the read-only shared resource.

Runtime Error 75 in Microsoft Excel

In rare occurrences, runtime error 75 will cause problems on other Windows systems. For example, later versions equipped with Excel 2000 Standard Edition have been known to generate this error. When a Visual Basic for Applications macros tries to use the Name statement, you may be presented with an error message that reads: Runtime error 75: Path/File access error. This error usually occurs for two reasons: the user tries to rename a directory with the Name statement, or a file in the directory the user is trying to change is set equal to the variable through the use of the “Dir” function.

To help you better understand this version of runtime 75, we will give a brief illustration. Let’s say you create a file named “file1.xls and save it in the “D:YourFolder” directory. From there, you run a macro comprised of the following statements:

X = Dir (”D:Yourfolderyourfile.xls”)

Name D:Yourfolder” As “D:Yourfolder”

When running such a macro, the runtime error 75 will almost always be displayed. One way to resolve this run time error is to work around the problem. In order to do so, you can use a dummy variable to set the pointer to a different folder. Using the example above, you can get around the run time error by composing your macro in the following way:

X = Dir (”D:YourfolderYourfile.xls”)

Y= Dir (”D:*.*”)

Name “D:YourFolder” As “D:Yourfolder”

For this macro, the “Y” variable is being used to reset the current directory. You can actually use the variable of your choice and reset it to any directory on your hard drive, with the exception of the one you are trying to rename.

Conclusion

Runtime error 75 is a bit more complex from a troubleshooting aspect but it can be resolved like many others. While the instances above are often the root of the problem, this run time error and several more are often caused by a congested registry or malware infection. To prevent such problems, it is best keep your system protected with a reliable registry cleaner and anti-virus tool. The registry cleaner will clear out the corrupt or missing entries in the registry while the anti-virus software will remove any malicious content from your system.

Jules Peters is a software engineer by profession.
She is now a full-time online technical writer at http://www.PCauthorities.com, where her mantra is repair Windows with me.

Hate the new Youtube channels? Block all ads on Youtube!