Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts!
X
Unfortunately it would involve modifying the XML of a regions, and so would involve a lot work.
Could base it on the Excel feature.
That could work. I prefer to avoid Excel as a solution though. If it is based on Excel it will only work for those that have Excel installed (which is most people, but not everyone), and calling an Excel based component involves a lot of overhead because it has to launch an Excel process.
That could work. I prefer to avoid Excel as a solution though. If it is based on Excel it will only work for those that have Excel installed (which is most people, but not everyone), and calling an Excel based component involves a lot of overhead because it has to launch an Excel process.
Agree, it does involve a lot of overhead but can be quite rewarding.
Find it a little strange that this type of feature hasn't been implemented. They are perfect for calculations or programs which are constantly used - easy way to notice unacceptable results.
That could work. I prefer to avoid Excel as a solution though. If it is based on Excel it will only work for those that have Excel installed (which is most people, but not everyone), and calling an Excel based component involves a lot of overhead because it has to launch an Excel process.
Agree, does involve a lot of overhead but can be quite rewarding.
Surprised this type of feature hasn't been implemented. Very good feature when using calculations or programs repeatedly and looking for unacceptable results.
No, it works the same way in all versions. Witout your swap of the arguments in "if" it shows what matches, rather than what does not match (which is what was wanted).
