Frustrated With Transfer Error . .

Evagrius

Registered User.
Local time
Today, 03:33
Joined
Jul 10, 2010
Messages
170
Hi All,

I can't understand why this is not working.

Code:
DoCmd.TransferSpreadsheet acExport, acSpreadsheetTypeExcel12, "qryMyResults", "K:\SouthWest\Analysis DB\Weekly test\Book1.xlsx", True

The code saves the file, but when I try to open it, I get an error message for an invalid format or file extension? What am I doing wrong? Thank you for any help!
 
Shouldn't it be .xls?

You have an older version of Excel
 
I have Excel 2007 on my computer though? If I change it to ".xls", when I open the file, it asks to convert? Do I need to remove 2003 from my computer?
 
Office does pose its problems when you're running two versions of the same application. You could try doing that.
 
I wouldn't run two versions of Excel (or Word, or PowerPoint, etc) on my computer. You are finding that you would have to open Excel 2007 and then open the file because it is using the last program opened for the default.
 
is there an excel97-2003 save option - that tends to be pretty flexible.

certainly opens in E2007 with no issues.
 
Fellas - thanks for the help. I send the DB to a co-worker who only has Excel 2007 and she received the same error when she tried to open the Excel file?
 
Well - If I change the extension to ".xlsb" then it works - I don't understand why though? I am happy it works! What is Binary intended for?
 
I just confirmed your issue with a sample of mine. I wonder if we have a bug. It shouldn't be that way.
 
Bob - I know you are good friends with the top Microsoft Programmers - can you give them a call and have them figure this out :)
 
I don't have access to them much anymore but I will start working it through the current MVP's who do have that access, or I have another idea - someone who posts here on the board might be able to help. :)
 
One can only conclude that the Excel file is corrupt.

But if it is then it is a bug which is causing it to be corrupt. It is a reproduceable problem. If you have Access 2007 and Excel 2007, try it, it will happen for you too.
 
Interestingly I can reproduce the same error. Most certainly a bug.
 

Users who are viewing this thread

Back
Top Bottom