NetTalk Central

Author Topic: ThisView{prop:filter}  (Read 4540 times)

clarion

  • Newbie
  • *
  • Posts: 14
    • View Profile
    • Email
ThisView{prop:filter}
« on: December 14, 2007, 07:48:58 AM »
Hi,

I`m quite new to Nettalk web, but here we go,

Using CW 6.3 (9057) & Nettalk 4.29

Have a table called overf where I want to filter on a cople of fields named Fort and Status, the value in the status field is 99 or 0 (zero) but the NetBrowse filter does not accept 0 in the status fileld.

Filter that shows "all" records
ThisView{prop:filter} = 'OVE:Fra_Lokasjonnr = ' & p_web.GetSessionValue('AKS:Kundenr') &' And OVE:Fort=0'

Shows records regardless of value in the status field, when I add the filter below, only record containing the value 99 shows, not the ones with the Statuts = 0

ThisView{prop:filter} = 'OVE:Fra_Lokasjonnr = ' & p_web.GetSessionValue('AKS:Kundenr') &' And OVE:Fort=0 And OVE:Status<=99' 

I Also tried
ThisView{prop:filter} = 'OVE:Fra_Lokasjonnr = ' & p_web.GetSessionValue('AKS:Kundenr') &' And OVE:Fort=0 And ( OVE:Status=0 or OVE:Status=99)

Same result, I have Offcource records with Status=0 (and fort=0 and Fra_lokasjonsnr = p_web.GetSessionValue xxx

???

Cheers
Tor-Bjarne

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: ThisView{prop:filter}
« Reply #1 on: December 17, 2007, 12:26:48 AM »
Hi Tor-Bjarne,

It all looks fine to me - there's no problem adding those fields to your filter.

The only possible flaw in your filter I can see is if the fields you're using in the filter have not been BIND'ed.  Does the bile have Allow Column Binding ticked on?

cheers
Bruce

clarion

  • Newbie
  • *
  • Posts: 14
    • View Profile
    • Email
Re: ThisView{prop:filter}
« Reply #2 on: December 17, 2007, 03:08:42 AM »
Hi,

Thank you for Your reply Bruce, now I have done some more research and found the error.

I have a key on the status field (for reporting) where the "Exclude Empty Keys" where ticked, this should not matter according to documentation (Filters are more flexible, since they don't require any special key manipulation, but they are much slower) but it does.

When I tick of this checkbox, recompile, my prop:filter starts working with the 0 value in the filter expression??

So next question (probably on the usergroup) is this behaviour a bug in 9057 or have I just completly missed the point from the documentation :)

Cheers
Tor-Bjarne