I have a report that takes about 50 minutes to run when using Table in JET. This report takes about 18 minutes to run when using Rows. However, I can't figure out how to have it retain the table functionality in Excel when using Rows. Right now, when I use the NL("Table") I can create Excel slicers directly on this data, but if I try to format in Excel to a table structure with Rows, Jet tells me to use Tables. I see there's slicer options in JET, but from what I can tell, they wouldn't apply here.
Date
Votes
2 comments
-
Jet Reports Historic Posts Hello.
You bring up some very interesting points.
Typically, NL(Table) is faster than using NL(Rows) simply because NL(Table) sends a single query while NL(Rows) can send several - although this is often mitigated by the optimizations built into Jet Professional.
When you use NL(Table) are you returning the *entire* table? or just a subset of the fields? What about when you use NL(Rows)?
What I'm driving at is that I could see this happening if I queried table that contained many fields and simply used: NL("Table","table name"). But, in my NL("Rows") - and probably NF() functions - I simply returned a handful of fields.
If that were the case, I would want to modify my NL(Table) function to only return the fields I needed.
If that is *not* the issue in your case, I would recommend floating this past Jet Reports Technical Support to have them take a look at the design and see what is going on. -
Jet Reports Historic Posts Thank you for your response.
When I'm using NL(table), I'm generally just returning a subset of fields based upon its joining to another table that will have my filtering criteria. I do the same thing with NL(Rows). The data I typically need to query is part of an add-on that we use in Navision, so a lot of the information I need seems to require the joining of multiple tables, as no one table has all the desired information.
Please sign in to leave a comment.