the error message i get is cant create the .xlsx file on this drive. Please choose a different disk.
This just means that wherever you have deployed this file, it cannot reach the target location.
Where have you setup your script to backup? You must ensure that the client can reach the target location, like a shared drive.
Why not use "Save a Copy As" instead? Just curious.
Cause if i do save copy as it just makes another version of the database. If i come out with a new version of the solution later on, i have to be able to import all the records into it. I dont understand how it cant reach the target location . On my admin account that is full access it works fine but after i wipe the full access admin account from the file the script has an issue.
The new admin account with custom credentials has access to all the tables, and can create and modify, exporting allowed.
Just wondering, with the account that is failing to work, did you try just one table and one set of records manually, and manually select the Excel File?
What I mean to say is this:
If I create a database with the following script on my computer:
This will work perfectly on my computer.
However, if I then move the FM file to another client's computer, the script will fail with the error you describe above because the directory does not exist.
If this is not the case then, I would ensure that the person logged into the computer has write access to the directory you plan to export the files to.
Are you sure that the path you use is also valid on the computer of your customer (Same Username?)
Normally you would create a valid path in a variable and use that path to export the file to.
Set variable[$path; "filewin:" & substitute( Get ( DesktopPath ) ; "Desktop/";"") & "File.xlsx"]
assuming they have writing rights to the C:/Users/Username path.
hope that helps
But you can easily import from a saved copy too.
It seems this is a Windows 10 issue. If i do it on a Windows 7 pro pc is works fine. Not sure whats causing it.