Both errors you are having, «Path/File access error» and «Run Time Error 75» are errors accessing the filepath, and they are likely being caused by the AutoRecover feature of Excel.
When you are leaving your Excel file for 20 minutes or so, the time limit for AutoRecover is reached. AutoRecover will then attempt to save AutoRecover information, in the case of your home computer it will be saving that to the Local drive, and at the office it will be saving to the network.
When an Excel file is open and AutoRecover is turned on, AutoRecover does not save the file until the first change is made to the file, the AutoRecover save time interval passes, and Excel has been idle for some time (the default is 30 seconds). (https://support.microsoft.com/en-us/help/289273/description-of-the-autorecover-functions-in-excel)
What is likely happening is a connection with your network is being interrupted, causing the AutoRecover to fail, which you won’t see until the ‘ActivateWorkbook’ event is triggered (which will show your userform, then crash).
(You can check your time limit for AutoRecover in Options>Save>Save Workbooks)
You might be able to work around the error by:
- saving the file to your local drive while you are at the office, or
- disabling AutoRecover for the workbook
- increasing the amount of time before the AutoRecover is triggered.
This user also found their errors were resolved by removing and repairing corrupt updates: https://www.mrexcel.com/forum/excel-questions/438888-intermittent-run-time-error-75-loading-form.html
Hope this helps!
 |
Номер ошибки: | Ошибка во время выполнения 75 |
| Название ошибки: | Path/File access error | |
| Описание ошибки: | During a file-access or disk-access operation, for example, Open, MkDir, ChDir, or RmDir, the operating system couldn’t make a connection between the path and the file name. | |
| Разработчик: | Microsoft Corporation | |
| Программное обеспечение: | Windows Operating System | |
| Относится к: | Windows XP, Vista, 7, 8, 10, 11 |
Анализ «Path/File access error»
Эксперты обычно называют «Path/File access error» «ошибкой времени выполнения». Чтобы убедиться, что функциональность и операции работают в пригодном для использования состоянии, разработчики программного обеспечения, такие как Microsoft Corporation, выполняют отладку перед выпусками программного обеспечения. К сожалению, иногда ошибки, такие как ошибка 75, могут быть пропущены во время этого процесса.
Ошибка 75 может столкнуться с пользователями Windows Operating System, если они регулярно используют программу, также рассматривается как «During a file-access or disk-access operation, for example, Open, MkDir, ChDir, or RmDir, the operating system couldn’t make a connection between the path and the file name.». Когда это происходит, конечные пользователи могут сообщить Microsoft Corporation о наличии ошибок «Path/File access error». Затем Microsoft Corporation может исправить эти ошибки в исходном коде и подготовить обновление для загрузки. Следовательно, разработчик будет использовать пакет обновления Windows Operating System для устранения ошибки 75 и любых других сообщений об ошибках.
Как триггеры Runtime Error 75 и что это такое?
Проблема с исходным кодом Windows Operating System приведет к этому «Path/File access error», чаще всего на этапе запуска. Причины сбоев обработки можно отличить, классифицируя ошибки 75 следующим образом:.
Ошибка 75 Crash — это распространенная ошибка 75 во время выполнения ошибки, которая приводит к полному завершению работы программы. Обычно это происходит, когда Windows Operating System не может распознать, что ему дается неправильный ввод, или не знает, что он должен производить.
Утечка памяти «Path/File access error» — Когда Windows Operating System обнаруживает утечку памяти, операционная система постепенно работает медленно, поскольку она истощает системные ресурсы. Потенциальные триггеры могут быть «бесконечным циклом», или когда программа выполняет «цикл» или повторение снова и снова.
Ошибка 75 Logic Error — Логические ошибки проявляются, когда пользователь вводит правильные данные, но устройство дает неверный результат. Неисправный исходный код Microsoft Corporation может привести к этим проблемам с обработкой ввода.
Как правило, ошибки Path/File access error вызваны повреждением или отсутствием файла связанного Windows Operating System, а иногда — заражением вредоносным ПО. Как правило, самый лучший и простой способ устранения ошибок, связанных с файлами Microsoft Corporation, является замена файлов. В качестве последней меры мы рекомендуем использовать очиститель реестра для исправления всех недопустимых Path/File access error, расширений файлов Microsoft Corporation и других ссылок на пути к файлам, по причине которых может возникать сообщение об ошибке.
Ошибки Path/File access error
Обнаруженные проблемы Path/File access error с Windows Operating System включают:
- «Ошибка приложения Path/File access error.»
- «Ошибка программного обеспечения Win32: Path/File access error»
- «Path/File access error столкнулся с проблемой и закроется. «
- «Файл Path/File access error не найден.»
- «Отсутствует файл Path/File access error.»
- «Ошибка запуска программы: Path/File access error.»
- «Не удается запустить Path/File access error. «
- «Ошибка Path/File access error. «
- «Path/File access error: путь приложения является ошибкой. «
Ошибки Path/File access error EXE возникают во время установки Windows Operating System, при запуске приложений, связанных с Path/File access error (Windows Operating System), во время запуска или завершения работы или во время установки ОС Windows. Выделение при возникновении ошибок Path/File access error имеет первостепенное значение для поиска причины проблем Windows Operating System и сообщения о них вMicrosoft Corporation за помощью.
Истоки проблем Path/File access error
Большинство проблем Path/File access error связаны с отсутствующим или поврежденным Path/File access error, вирусной инфекцией или недействительными записями реестра Windows, связанными с Windows Operating System.
В основном, осложнения Path/File access error связаны с:
- Поврежденные ключи реестра Windows, связанные с Path/File access error / Windows Operating System.
- Зазаражение вредоносными программами повредил файл Path/File access error.
- Path/File access error злонамеренно или ошибочно удален другим программным обеспечением (кроме Windows Operating System).
- Другая программа находится в конфликте с Windows Operating System и его общими файлами ссылок.
- Поврежденная загрузка или неполная установка программного обеспечения Windows Operating System.
Продукт Solvusoft
Загрузка
WinThruster 2023 — Проверьте свой компьютер на наличие ошибок.
Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
Permalink
Cannot retrieve contributors at this time
| title | keywords | f1_keywords | ms.prod | ms.assetid | ms.date | ms.localizationpriority |
|---|---|---|---|---|---|---|
|
Path/File access error (Error 75) |
vblr6.chm1011249 |
vblr6.chm1011249 |
office |
5c1e151a-facd-6e55-d075-f7faef4a2793 |
06/08/2017 |
medium |
During a file-access or disk-access operation, for example, Open, MkDir, ChDir, or RmDir, the operating system couldn’t make a connection between the path and the file name. This error has the following causes and solutions:
-
The file specification isn’t correctly formatted. A file name can contain a fully qualified (absolute) or relative path. A fully qualified path starts with the drive name (if the path is on another drive) and lists the explicit path from the root to the file. Any path that isn’t fully qualified is relative to the current drive and directory.
-
You attempted to save a file that would replace an existing read-only file. Change the read-only attribute of the target file or save the file with a different file name.
-
You attempted to open a read-only file in sequential Output or Append mode. Open the file in Input mode or change the read-only attribute of the file.
-
You attempted to change a Visual Basic project within a database or document. You can’t make design changes to the project.
For additional information, select the item in question and press F1 (in Windows) or HELP (on the Macintosh).
[!includeSupport and feedback]
Hi,
I’m trying to copy files selected in the openfiledialog to c:Rawdata.
The code below causes the Run-time error 75.
Public Sub GetFiles()
Dim fDialog As Office.FileDialog
Dim fso As New FileSystemObject
Dim Path As String
Dim Filename As String
Dim varFile As Variant
Set fDialog = Application.FileDialog(msoFileDialogFilePicker)
With fDialog
.AllowMultiSelect = True
.Title = «Please select one or more files»
.Filters.Clear
.Filters.Add «CSM Files», «*.TXT»
Path = «C:RawData»
If .Show = True Then
For Each varFile In .SelectedItems
Filename = varFile
FileCopy varFile, Path
Next
Else
MsgBox «You clicked Cancel in the file dialog box.»
End If
End With
End Sub
From what i’ve read on-line the error relates to permissions or lack of source file. The file clearly exists and I can copy and paste the file to the destination directory from within the open file dialog window so I can’t see a permissions issue. I’m very
new to VBA, and I’m probably missing something that should be obvious.
Any advice much appreciated
- Network Installation, New or Changed Configuration
- New Server
- Data on Different Server
- Error Message Refers to “CFSSTRT”
- New Workstation, Especially Windows 7
- Program Works for One Person but Error 75 for Another
- Single-User
- Network
- Database Is Effectively Read Only
- Restore/Import from diskette
- Restore from a CD/DVD
- Some Programs Work, Some Don’t
- Antivirus Software: Comodo, Avast, Bit Defender, StopSign
- Backup Software
- None of the Above
Error 75 usually indicates a rights issue. The most common problem is that the logged on user does not have the right to modify files in the designated folder. There are, however, a number of other situations that can cause this error. All are listed below, along with appropriate solutions.
Most of the following solutions involve changing security and sharing permissions on the CFSLIB folder. Controls for setting these permissions may be different, depending upon the operating system. The controls are generally accessed by right-clicking on the folder and left-clicking on «Properties.» Then look for:
- Tabs labeled «Security» and «Sharing,» or
- Check boxes labeled “Let network users access my files” and “Let network users modify my files.”
Network Installation, New or Changed Configuration
The network version of a CFS program allows the data to be stored in a shared folder, preferably by use of a mapped drive letter. The shared folder can be located on an actual server that is not used as a workstation, or it can be on someone’s computer in a peer-to-peer configuration. The shared folder must have «Sharing» and «Security» permissions set to allow users to «Modify» or «Change» files within the folder.
New Server
If error 75 occurs while you are trying to implement a new server, make sure permissions on the shared folder are set correctly. For more information, see How do I map a network drive?
Data on Different Server
The default configuration for CFS programs has the database folder within the program folder. The program can be configured so that the program is installed on one computer and the data is stored on a different computer/server. If this is the case, and the drive letter previously assigned to the old server is no longer available, the attempt to reach the old drive letter can result in error 75. For this situation, try the following:
- On program startup, add a new user. This new user will be assigned a default database path.
- Click «Configuration» on the program toolbar to open the «Configuration Options» screen.
- Under «Data Options,» change the «Data Path» to the correct path.
Error Message Refers to “CFSSTRT”
See the following section.
New Workstation, Especially Windows 7
Since 2009, CFS programs place a footprint on the workstation: the contents of the CFSLIB folder at the root of the operating system drive (normally C:CFSLIB). This folder may inherit security settings from the root of the drive, including a setting which restricts “Modify” to administrators. Users of CFS programs do not have to be administrators, but they do need «Modify» permission on CFSLIB and all contained folders.
Generally, for Windows XP and later, the C: drive is formatted as NTFS. If some users cannot write within the C:CFSLIB folder but others can, open the «Properties» dialog on the CFSLIB folder and select the «Security» tab to select “users” of the machine and check the “Allow Modify” box.
If the «Security» tab is not present in the «Properties» dialog, “Simple File Sharing” is probably in effect.
- If the operating system is XP Professional or Windows 7, go to Tools – Folder Options – View tab. At the bottom of the list, remove the check from the «Simple File Sharing» check box.
- If this is XP Home edition, shut down the computer and reboot in Safe Mode. (See How do I install a program or update in «safe mode?») You will then be able to select the «Security» tab in the CFSLIB Properties dialog.
Program Works for One Person but Error 75 for Another
Single-User
In a single-user environment, this issue may be due to the program having been installed when someone was logged on as “administrator.” The program works as long as «administrator» is logged on to the computer, but when another user is logged on, the program fails with error 75.
The solution is to log on as administrator and open the «Properties» dialog for the C:CFSLIB folder. On the «Security» tab, add a user with the name “everyone” and edit permissions to allow the user to «modify» or «change.”
Network
In a network environment, start by performing the above procedure to give «everyone» modify or change permissions at the workstation. Then, do the same thing for the shared folder at the server:
- Locate the shared folder (CFSLIB).
- Right-click on the folder and left-click on «Properties.»
- Click the «Share» tab and the “Permissions” button.
- Add a user “everyone” and give that user “allow modify or change” under the share permissions.
Database Is Effectively Read Only
All users must have «Modify» permissions for CFSLIB and included folders. However, the database might not be in the same folder as the program. For example, in some network environments, the CFSLIB folder with the program is installed on one server, while the data is stored on a different server. In that case, the security and sharing permissions on the shared folder containing the database must also allow «Modify» for all users of the program.
This has also infrequently been caused by other software interfering with the database file in network installations. Check for automatic backup and/or antivirus software running on the same computer. It may be necessary to add an exemption for our software in your antivirus system and/or exclude the network’s CFSLib directory from automatic scanning/backups.
Notably, we have seen this issue with Norton360 and Webroot Security.
Restore/Import from diskette
If error 75 is encountered while attempting to restore or import from a diskette, it could mean that there is a bad drive, a bad diskette, or the protection switch is set on the diskette.
The solution is:
- Create a temporary folder on the hard drive and try to copy the contents of the diskette to that folder.
- If the copy is successful, open the «Properties» dialog for the temporary folder and make sure the «Read-only» attribute checkbox is cleared.
- Try the restore/import from the temporary folder.
Restore from a CD/DVD
If error 75 is encountered while attempting to restore or import from a CD/DVD drive, it could mean that there is a bad drive or a bad medium. The usual error on attempting to restore from a read-only device such as a CD or DVD is error 3051.
The solution is:
- Create a temporary folder on the hard drive and try to copy the contents of the CD or DVD to that folder.
- If the copy is successful, open the «Properties» dialog for the temporary folder and make sure the «Read-only» attribute checkbox is cleared.
- Try the restore/import from the temporary folder.
Some Programs Work, Some Don’t
If some program work for a user, but others fail with error 75, it’s possible that a sub-folder of CFSLIB has the «Read-only» attribute set, or does not have the necessary «Modify» permissions.
- Open the «Properties» dialog for the failing program’s folder by rIght-clicking on the folder and left-clicking on «Properties.»
- Make sure the «Read-only» attribute checkbox is cleared.
- Make sure the «Security» settings on the folder include «Allow Modify» for the applicable user or group.
- Click «Apply» to apply the settings.
If there is no Security tab in the Properties dialog, go to Tools — Folder Options — View tab. Look for a «Simple File Sharing» check box, and remove the check from that box. The Security tab should then be available.
Antivirus Software: Comodo, Avast, Bit Defender, StopSign
There have been numerous occurrences of conflict between the above antivirus programs and CFS software (especially Payroll System), resulting in errors 75, 3049, 3050, and 3051. If one of the above antivirus programs is in use, exemptions or exclusions must be set so that they do not interfere with the database folder (e.g., PR2010DB). If the error occurs during backup, the solution is to exclude the entire CFSLIB folder.
Backup Software
Backup software can be configured to back up data continuously as you work, either to an external drive or the cloud. This can cause a conflict with CFS programs, especially Payroll System. As with antivirus software, it is necessary to exclude the database folder from the backup operation.
If the CFS program is set to automatically back up the database on exit, your backup software can include the resulting backup folder, so that backup protection is not lost.
Another workaround is to pause the backup software while payroll data entry is in progress. When you restart the backup software, it will catch up with changes made while it was paused.
None of the Above
If changing the security settings for the folder has not solved the problem, use the following procedure to make sure the «Read-only» and «Hidden» attribute checkboxes are cleared for CFSLIB and all subfolders.
In a network installation, first perform the procedure on the CFSLIB folder on the server. If that does not solve the problem, perform it on the C:CFSLIB folder(s) on workstation(s).
- Open the «Properties» dialog for the CFSLIB folder by rIght-clicking on the folder and left-clicking on «Properties.»
- Click in the «Read-only» checkbox until it contains a black check mark; do the same for the «Hidden» checkbox.
- Click the «Apply» button and select the «all files and folders» option.
- Click again in each of the «Attributes» checkboxes to clear them.
- Click the «Apply» button and select the «all files and folders» option.
The “Read-only” checkbox has three possible status indications: clear, black, and shaded. If the box is shaded, it means some, but not all, items in the folder are read-only. This does not necessarily mean there is a problem; the items may be system files.