Jump to content
Salesforce and other SMB Solutions are coming soon. ×

Exporting to Excel Error.


Tri3

Recommended Posts

When I try to Export a table to Excel I get an error message saying

 

"Name of File.xls" could not be created on this disk. Use a different name, make more room on the disk, unlock it or use a different disk.

 

Has anyone run into this problem. I am able to export tables using the other formats. I only get this error when trying to export to excel.

 

Also is there a way to export all the tables at once?

 

Cheers

Link to comment
Share on other sites

Manually or via script? Windows, yes? FileMaker 9?

 

(There is a known issue with MacOS X 10.5.x and Excel exports, if you're NOT using Windows as described in your profile please tell us)

Link to comment
Share on other sites

Usually when I encounter that error message it is happening because I already have a file with that name and Excel currently has it open. If you close Excel your new file should overwrite the older file but if Excel has it open you will see that error message.

Link to comment
Share on other sites

Update to the latest FileMaker 9, I believe it's 9.0v3; but I've heard some folks say they still have problems exporting to Excel from FileMaker under Leopard.

Link to comment
Share on other sites

"Name of File.xls" could not be created on this disk. Use a different name, make more room on the disk, unlock it or use a different disk.

How are you performing the export? Scripted or manually (as previously asked). If it is scripted I would look at your export path. I have seen this error before when exporting any type of file if the path is incorrect (share point not mounted or you dont have write access to that particular folder (eg the System folder)

Link to comment
Share on other sites

  • 1 month later...

Hi to all. I got the same problem, i've tested on OSX 10.5.2 FM Pro Adv 9.0v3, Win XP SP2 FM Pro 9.0v3. I've performed the export manually and within a script but I got the same problem... I've noticed that deleting the preferecences file and restarting the application, the problem is solved but only for a few times... smiley-cry

Link to comment
Share on other sites

  • 3 weeks later...

If I read your post correct, excel had the file open. The error is happening because the file is open. Excel locks the file when it is being used. The export from FMP is trying to replace the file with the one it is creating.

 

Close the file and see if you still get the error.

Link to comment
Share on other sites

Hi everybody, i've tried in every condition but the problem still remains. Excel is closed, FM is the only active application. It seems like FM doesn't have any permission to create the file. I've modified those permissions for the Desktop but the problem is still the same. Any suggestion?

TIA

 

smiley-cry

Link to comment
Share on other sites

Hi to all. I got the same problem, i've tested on OSX 10.5.2 FM Pro Adv 9.0v3, Win XP SP2 FM Pro 9.0v3. I've performed the export manually and within a script but I got the same problem... I've noticed that deleting the preferecences file and restarting the application, the problem is solved but only for a few times... smiley-cry

 

To exactly what path are you trying to export?

Link to comment
Share on other sites

That's not the answer to the question that I asked. I want the exact character-for-character string to which you are exporting, exactly verbatim the way it is typed in your script.

Link to comment
Share on other sites

Hi this is the full path name for the file:

filemac:/Macintosh HD/Users/fabrizio/Desktop/prova.xls

i got the same result if i try to export manually the records to the file...

 

I'm using FM9.0v3ADV on my MacBook Pro with Leo 10.5.3. It's just the same on Winzoz XP SP2 and FMPro 9.0v3

 

TIA smiley-undecided

Link to comment
Share on other sites

OK that's quite odd. If it were only Leopard I'd blame Leopard. If it were a calculated path I'd tell you to use a variable. If it were only in a script I'd assume something was amiss in your script even if it weren't yet obvious what. If it were only on one computer I'd wonder if perhaps the error dialog might even be right and you were way short on disk space.

 

a) Are you using Export Records [selecting Excel as the format] or are you using Save Records as Excel?

 

b) Can you export to any path whatsoever?

 

c) If you modify what table you are exporting from, or try a totally different filemaker file to export from, does it still throw the error or is it unique to this table of this file, or to this file generically, or to this found set of this table of this file, etc?

Link to comment
Share on other sites

Hi AHunter3

Sorry to bother you... Ok let me answer to you:

 

“OK that's quite odd. If it were only Leopard I'd blame Leopard. If it were a calculated path I'd tell you to use a variable. If it were only in a script I'd assume something was amiss in your script even if it weren't yet obvious what. If it were only on one computer I'd wonder if perhaps the error dialog might even be right and you were way short on disk space.”

 

-No it happens on several Mac/PC

-Yes i got enough space to export the file

 

 

“a) Are you using Export Records [selecting Excel as the format] or are you using Save Records as Excel?”

 

-It happens on both

 

“b) Can you export to any path whatsoever?”

 

-yes i did it but no way out

 

“c) If you modify what table you are exporting from, or try a totally different filemaker file to export from, does it still throw the error or is it unique to this table of this file, or to this file generically, or to this found set of this table of this file, etc?”

 

-yes it happens on every file and every table i’ve created

 

TIA

Opps!

Link to comment
Share on other sites

Hmm.

 

Well I've got 9.0v3 and I can export to Excel. So there has to be something different between your set up and mine. Can't be computer-specific since it's doing you in on windows as well as MacOS.

 

Your location is Rome - Italy. Are all of these installs on Italian-language computers? If so, can you get your hands on a computer with a different language set up (English, Dutch, etc)? I can't imagine why that would make a diff but all the obvious stuff has been ruled out at this point...

 

Are you in a position where you could, on a temporary basis, allow one of us to open your file as a guest and try exporting to Excel from your database using our copy of FileMaker (and therefore our settings / operating system settings) and see if that works?

Link to comment
Share on other sites

Manual export from your file: worked perfectly.

 

Running the Export script you wrote in your file: also worked perfectly.

 

 

My environment: MacOS X 10.4.11, PowerPC, English (American) language OS, FileMaker Advanced 9.0v3 also English language.

Link to comment
Share on other sites

Ok i think that i've solved the problem for Leo... The problem seems to be located in the preferences file of FM. Basically FM seems to store the last root directory in a key (NSNavLastRootDirectory). If you modify this key from the value that you find in with the "~/Desktop" (without quotes), the export works well. I've tried to do the same thing for Win but i didn't find any key with regedit within the registers. Any suggestions? Oh Really!

 

TIA

Link to comment
Share on other sites

  • 1 month later...
Can you tell me where to locate the preferences file? I've just started having this problem too. It wasn't a problem until tonight.

 

 

I you can find the com.filemaker.pro.plist following this path:

/User/Library/Preferences

 

open the file with Property List Editor 2.2 and patch it as I wrote.

Bye

smiley-smile

Link to comment
Share on other sites

Thanks for your post but as mysteriously as it started last night so too did it end. The only thing I did that may have had an impact (and I have no idea how) we restart my Time Capsule. I only save my files on my local drive so I'm not sure how (or if) the 2 are related but as soon as Time Capsule came back online it worked like a charm.

 

Anyone know if this had anything to do with the problem or correction?

 

TIA

David

Link to comment
Share on other sites

you're welcome... no idea about time capsule can interfere with the problem... maybe the backup procedure has unlock something at the privileges level of the file...

Link to comment
Share on other sites

This thread is quite old. Please start a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

Terms of Use