Any chance the file is opening "read only"?--I'd expect the user would get a warning message when they open the file though. I'm not a Vista user, but other posters have reported that they had to make sure that the database file was located in the correct location before they could "write" to the file.
The issue is not the File Attributes...
I'd had the customer check the files' attributes first thing.
Read-Only is unchecked on all of them.
Can you tell me more about "Vista and the correct location before they could "write" to the file."
(I didn't find your reference when searching for hese terms)
You might want to check their account settings as well.
This is the thread I remembered, I'm not sure that it's applicable though...
The URL you provided contained a kernel that helped me resolve the issue.
FileMaker Product(s): FileMaker Pro 10.0v3
Operating System(s): Windows Vista
The issue does not happen under Windows XP, Service Pack 3
Description of issue:
The New Record command is deactivated (grayed out) when FielMaker data files (.fp7) are located inside the Program Files folder under
Thus, the user is unable to created new records.
Windows' Vista limits write to commands within FielMaker files (.fp7) located in the Program Files folder.
This appears to be related to Vista rules/use of items in the Program Files folder.
(I am not a Vista user.)
Workarounds that you have found:On Windows' Vista, locate FileMaker (fp7)data files to My Documents, or elsewhere.
Do not locate FileMaker (fp7) data files to Vista's Program Files folder.
I'd appreciate some verification/elaboration from FileMaker 10 + Vista users.
Why would you put a database file inside the Program folder? That seems an unusual place to put data files.