Memory error - can't export to Excel

Are you sure that's a QB message? Could it be an Excel message?

Can you start Excel by itself?

Can you export the report to a CSV file, then import the file into Excel?

Yes. I opened Excel and tried to export. It still said it couldn't open Excel. I even opened a bunch of other programs; plenty of memory. I restarted and only loaded QP - same thing.

I also use 123, so I exported the report as a *.prn file and then opened and saved it as a *.123 file.

??? What were you trying to export from an opened Excel program?

"It" what?

Cool, but no one cares about 123. Can you export the repot to a CSV file, then import the file into Excel? Specifically:

1. Export the report as a CSV file.
2. Close QB.
3. Open Excel.
4. Import the file from step one.

Does this happen on all reports? The process works as advertised here.

Sounds like you may need to re install QB. It's possible its export function got trashed. I'm assuming by all you mean all including super small reports.

Before reinstalling, as mentioned later in this thread, I have a few questions for you:

1. What QuickBooks release are you on (R1, R2, R3, R5, R6, R7)? ...you can find this by hitting F2 when you have QuickBooks open - it's reported on the first line. If you're on an earlier release - go ahead and update to R7.
2. Did it ever work? ...If it did, can you think of anything that may have changed on your system?
3. If you boot into safemode, and try it again - does it work? (Tap the F8 key when booting the machine and select Safemode)
4. What version of Excel are you using?
5. What exactly in QuickBooks are you trying to export to Excel? Can you export *anything* to Excel?

No. I tried to export a report from QB to Excel with Excel open. Even though Excel was open, QB said it could not open Excel.

QB

Well I do, but that's irrelevant. What I want to know is why QB thinks I'm short on memory when I'm clearly not.

Sure, but again, that's not what I'm concerned about.

You aren't low on memory. A specific part of the process of sending a file to the O/S and requesting it start and notify Excel of the file is giving a false indication that memory is low and not reporting the correct error number back to QB!

There it is. He f***ed one of the registry keys about how much RAM to give a context switch. My guess is QB needs more than the recommended minimum and sets the key that way on install.

What do you suppose might cause a thing like that?

Yeah, it doesn't matter how small the report is. I can work around it, (it will export *.csv and *.prn) but it is disturbing when a program ya count on starts acting up. I can't figure out why it thinks I'm low on memory.

(I sit waiting for the dreaded other shoe to drop. )

QB Pro 2006 - R7

Yes, it worked fine.

Unfortunately yes. A guy, contracted by Dell, installed a network. He had all kinds of trouble and I can't be sure what he might have mucked up. (Although I'm not sure how he could have affected one particular function of a program that he didn't mess with - there are no other issues that I am aware of yet.)

I haven't tried that. I give it a try later.

Excel 2003 (SP2)

I tried various reports. No it claims it can even open Excel (even if it's already open)

So a reinstall is my best bet?

replying to GWB, Jill wrote: I'm not saying this will work for this but it did for me. I repaired Office and it started working again. Now this link wanted me to do the Online Repair which I actually didn't do. I did a Quick Repair which worked. If Quick Repair doesn't work then I'd try the Online Repair.