-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can I turn off the delete_registry #1
Comments
Hi, you could try:
Just set the |
Thank you for your reply. I have been trying to use convert_xls_as_xlsx: if I declare delete_registry = FALSE or TRUE I get an error message convert_xls_as_xlsx(input_dir = wd,
Error in convert_xls_as_xlsx(input_dir = wd, export_dir = wd, office_folder = "C:/Program Files/Microsoft Office/root/Office16", : If I don't use the argument delete_registry I get the following convert_xls_as_xlsx(input_dir = wd,
Warning: Converting xls to xlsx (1/16): Deleting registry entry: The code will cycle through my list of xls files and not convert any, after about 30 seconds the error message is delivered and the code moves on to the next file. Kind regards Charles |
I did as you suggested and created a new function with delete_registry=FALSE, it stopped the error that I was getting but the function is still not converting my files. Everything runs but nothing changes in my destination folder.
Converting xls to xlsx (1/16): Converting xls to xlsx (2/16): Kind regards Charles |
Hi, I have alot of old xls files that need to be converted to xlsx and have used your function previously. The code I have written works on my machine at work but with working from home at the moment I am getting an error to do with deleting the a registry key and the code failts to convert my xls files. The error is:
reg delete HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Resiliency\StartupItems /f
ERROR: The system was unable to find the specified registry key or value.
I Have checked the registry and the Resiliency Key does not exist, which is obviously the reason for the error. Can you suggest a work around please?
Kind regards Charles
The text was updated successfully, but these errors were encountered: