Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VFP & Excel 2010

Status
Not open for further replies.

whateveragain

Programmer
Apr 20, 2009
92
US
VFP works fine with Excel 2010 on most machines except for one client. Unfortunately, I don't know what OS. She keeps geting a 'detail band is too large. I shrunk the report in question and she's still getting this error. I told her to try it on another printer. To my knowledge, she didn't have any problems with this app until she changed Excel. Any other ideas?
 
Further to the use of Excel 2010..

I have a User who is complaining that the ShellExecute(0,cAction,(myshowitfile),"","",1) with (myshowitfile) being the full path with the xls extension does not open the document but comes up with a dialogue ( I think to select a file).

Everything works correctly here under Office 2002.

Has anything changed or is it a user error?

Thanks
Coldan
 
"She keeps getting a 'detail band is too large. I shrunk the report in question and she's still getting this error."

whateveragain - What does this have to do with the combined topics in the title of this posting - VFP & Excel 2010

How is Excel involved at all.

If posting #1 has nothing to do with Excel, then this posting is mis-labeled. Yes, the 2nd posting by another forum user goes into an Excel topic, but what does that have to do with posting #1?

Good Luck to both of you.
JRB-Bldr

 
I agree with Mike and JRB.

Whateveragain: The message "Detail band too large" is issued by VFP when you preview or print a report (an FRX file). You need to investigate the report itself rather than any Excel interface.

Coldan: I suggest you start a new thread, with a meaningful title. We will reply to the question in that thread.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business
 
Actually, I can see where both of these issues may be loosely valid here, since they both mess with VFP and automation after upgrading. Two separate threads would have been more informative in the future though.

But anyway, for the first post, upgrading Excel could mess with reports if the installation modified or added any printer drivers, changed any fonts, or that sort of thing.

As for the ShellExecute not working after an upgrade, there are other threads regarding that issue in this forum so I don't think that needs to be covered again.



-Dave Summers-
[cheers]
Even more Fox stuff at:
 
upgrading Excel could mess with reports if the installation modified or added any printer drivers, changed any fonts, or that sort of thing.

You might be right, Dave. It's certainly a possibility.

On the other hand, we don't at this stage know if there is any connection between the Excel upgrade and the VFP error.

All that the original questioner told us was that the user "didn't have any problems with this app until she changed Excel". We don't know what other changes took place at around the same time. If it was me debugging this problem, I'd want a bit more evidence of a link between the upgrade and the error.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business
 
I have now tested my app with Office 2007 and my user was mistaken.

All is still well...

Coldan
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top