tvoss wrote:
Okay that's great that I can upgrade now, but do I just download the demo?
Please help me with this issue.
Just go to the Customer Area, and download the version you want to upgrade to, e.g. 2.6 at the left of the customer area menu.
I read into those linq articles you mentioned, but I'm not really getting to my question.
I'm already using Linq to objects with llblgenpro collections to reduce properties and resort, refilter for reuse.
How is 2.6 going to help when it already seems to work?
The thing is that v2.0's DbFunctionCall could just handle a function name and that's it. V2.5 introduced formatted SQL text, so you can use the DbFunctionCall to produce custom SQL snippets, like a CASE statement. So to use this feature, you need v2.5 or higher, otherwise you can't write code which produces the SQL snippet you want (the CASE statement).
Also, if I get a filtered collection of 40,000 transactions that have a lot of fields, then use Linq to objects to get a 2 fields version of that collection before I've done anything else with the original collection, is memory usage helped by such a maneuver?
Thanks,
Linq to Objects makes copies of objects, so the data is copied.
In v2.6, you can use Linq queries instead of predicates and the like to filter databases, and we have build in support for IIF (the VB statement) in Linq queries in v2.6
Please read the 'migrating your code' section in the documentation to learn more about what will break, what to look out for etc.