DavidEman Posted March 12, 2008 Posted March 12, 2008 I've got a solution setup where the database is residing on a shared drive (for security reasons) and the database is being opened single user. I have a script run that automatically exports records to a text file on the user's desktop. I get a write error when it tries to run the export (not enough room on the drive, change the name, etc.). When I move the database to the C: drive, it exports fine. We are running Windows XP. Anyone have any idea how to get this to work without moving the file to the c: drive? Thanks for your help.
Colin Keefe Posted March 12, 2008 Posted March 12, 2008 I've got a solution setup where the database is residing on a shared drive (for security reasons) and the database is being opened single user. Unless this shared drive is in your physical machine, this is a bad idea. Having the drive shared in the first place is a bad idea too for other reasons, though I assume you're doing this solely to keep data on a secure server - not to actually share. I have a script run that automatically exports records to a text file on the user's desktop. I get a write error when it tries to run the export (not enough room on the drive, change the name, etc.). When I move the database to the C: drive, it exports fine. We are running Windows XP. Anyone have any idea how to get this to work without moving the file to the c: drive? Thanks for your help. What version of FileMaker are you using? And how are you constructing the path to the desktop?
DavidEman Posted March 12, 2008 Author Posted March 12, 2008 Yeh, I'm not too happy with the setup, but they want a secure server. The DB isn't shared, only used by one person. We are using FMP 9 Advanced - latest update, I think. In a script, I am setting a variable to 'file:../Desktop/FileName.txt' Is that my problem?
Colin Keefe Posted March 12, 2008 Posted March 12, 2008 Possibly. I'd try something like: Get ( DesktopPath ) & $filename If more than one person has access to that shared directory, I'm not sure it really classifies as a "secure" server. But I won't quibble about it. My main point is that you run increased risk of file corruption when the disk read/write instructions have to pass from the host application (in this case you) over a network to a remote drive.
Recommended Posts
This topic is 6100 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now