What steps will reproduce the problem?
var test =
from c in linqtoexcel.WorksheetRange<TestClass>("A8", null, "TestWorksheet")
select c;
What is the expected output? What do you see instead?
I expect either:
1. An appropriate error for the null endRange parameter.
2. The query to execute, substituting an appropriate end range.
Instead the error gets caught at line 176 of ExcelQueryExecutor.cs, where the
catch statement assumes that the name of the worksheet is incorrect. This
actually hides the real error which looks like it is due to the end range
argument being excluded:
The Microsoft Access database engine could not find the object
'TestWorksheet$A8:'. Make sure the object exists and that you spell its name
and the path name correctly. If 'Consignment Report Apr - 12$A8:' is not a
local object, check your network connection or contact the server administrator.
What version of the product are you using? On what operating system?
1.6.2, x86
Please provide any additional information below.
I guess this issue would probably occur for a null start range as well. Is it
possible to automatically detect the range that has been used in the
spreadsheet, so that the endRange parameter can be ommited?
Also is it possible to specify only rows or column names for the range? Is the
range address format documented anywhere?
Thanks,
Tim
Original issue reported on code.google.com by tim.sirm...@gmail.com on 11 May 2012 at 12:22
Original issue reported on code.google.com by
tim.sirm...@gmail.com
on 11 May 2012 at 12:22