Skip to main content

2 replies

M
MikeArmstrong1-Visitor
1-Visitor
April 10, 2012

I haven't got Mathcad at the moment but I've heard of a similiar issue before.

I you using Origin = 0?

Mike

M
MikeMcDermott1-VisitorAuthor
1-Visitor
April 10, 2012

I have origin set to 0 and setting it to 1 makes no difference.

M
MikeArmstrong1-Visitor
1-Visitor
April 10, 2012

Your correct Origin has no bearing on the component, but I'm sure Excel components have Origin = 1 built in.

Mike

A
AndyWesterman12-Amethyst
12-Amethyst
April 10, 2012

One note - If you add an entry in the B1 cell the readexcel gives the correct result.

It works the same for mathcad 15 & prime2 so the same bug probably exists in both.

Andy

M
mzeftel1-Visitor
1-Visitor
April 10, 2012

Andy and Mike,


I see the same thing you do for XLS files (Excel 2003). READEXCEL works correctly for XLSX files (Excel 2007 and Excel 2010.(

If I add an entry to B1 in the XLS file, Mathcad grabs the correct cell, if B1 is empty, then it grabs the value one cell down.


I'll log this if it is not logged already.

Thanks,

Mona

M
MikeArmstrong1-Visitor
1-Visitor
April 10, 2012

Mona,

I'm not sure if the issue has been logged. The thread I previously came across this issue was one of Raiko's threads using scripted components.

Mike

Terms & ConditionsAccessibility statement