Most likely cause is a change in the file path to the old version--something that is saved in the Import Records script step. A change in folder or file name is all it might take to cause this. You can try updating your import script to reconnect to the old file and see if that corrects the issue.
I have plugin, both from Mac and Windows that the import script will open to allow the user to select the file for import. The script then contracts the path and the rest is done through the import function. It has been working well for some time on both platforms. I assume that something is changed within windows that is stopping the file from importing. Perhaps a security feature or write protection, on teh file locations, not the database.
I can still add new records to the database....
I wouldn't think so, given that you are able to add new records, unless a folder permission setting is keeping the user from even opening the original file--which seems unlikely here.
Here's how I automate the import process without needing a plug in:
- Use Insert File to insert the original file by reference into a container field. This can be set up to pop up the open file dialog so that the user can find and select the original file.
- Use text functions to extract the file path from this container field and store it into a variable.
- Import the records from this older file, by referring to the variable.
You might test that approach to see if there are any issues with the plug in you are currently using.