PB 10.5.2, Build 7662

If dw_1.SaveAs("", Excel!, True) fails,

is there a way to determine the exact error?

TIA

Ken

Ok, added simple return code check to report when ftn does

not work.

User originally said: 'Saveas no longer works.' Found out

later that it 'works once, then quits.' Using the same

parms in the ide, I some found that the times it 'does not

work' is when the dw contains more than 65,536 rows -

Excel's (2003) limit. Excel 2007 will have an increased

limit, if we ever go to it.

I thought Saveas() just built a file, but it must either

connect to Excel to check the limit or have the limit

built-in to the ftn. Wonder if it will work properly with

Excel 2007?

HTH someone.

Ken

The limit is built into the function. It just adheres to MS specifications.

You don't require Excel to be installed on your computer to use.

--

Terry Dykstra (TeamSybase)

http://powerbuilder.codeXchange.sybase.com/

http://case-express.sybase.com/cx/welcome.do

http://my.isug.com/index.php?mo=is&op=in

I understand now that a Excel 2003 worksheet row limit is

65,536 rows,while Excel 2007's is 1,048,576 rows.

So would this ftn limit the save to 65,536 rows or would it

allow more than that, if you do have Excel 2007 installed?

I don't want to tell the user that installing Excel 2007

would solve the problem, if it doesn't.

Thanks

Ken

it doesn't.