Prev: Navision version 5.00 Job Queue
Next: Command Line Options for Navision 5.0 Setup
From: victorcoder on 25 Jul 2007 11:38
Hi Brett,

I have found your question because I've the same problem with dates
ranges in SQL against the Nodbc, if look at the Nodbc manual included
in the NAV DVD you can find the following:

"Important
If you want to filter using a date range, you must use the
SetFlowFilter predicate.
However, when you use this predicate you can only specify one date
range per filter
and you therefore cannot set filters that specify more than one date
range.

The SetFlowFilter predicate is maintained for backwards compatibility
and to
support date ranges."

So I do queries with SetFlowFilter in this format:

pred SetFlowFilter, '<TableName>', '<FieldName>', '010101..310101'

Hope this helps.



Brett Haydon ha escrit:
> Hi we are doing a 2 stage upgrade from 2.6 Native to 4.0SP2 Native then
> converting to SQL 2005.
>
> Until we finally migrate the database to SQL 2005 we are stuck using some
> existing Excel queries through the N/ODBC interface, but some of the
> functionality from 2.6 seems to have been removed in 4.0.
>
> In v4 it doesn't seem possible to set a date range on a flow filter in
> N/ODBC. If someone can prove me wrong and show me how this is done I'd be
> most appreciative.
>
> I have managed to do a single date filter using {pred SetFlowFilterMultiple,
> Item."Date Filter",21062007} which works but any variation on a date range
> doesn't.

From: Brett Haydon on 25 Jul 2007 19:14
Don't know how I missed that..

thanks.

"victorcoder(a)gmail.com" wrote:

> Hi Brett,
>
> I have found your question because I've the same problem with dates
> ranges in SQL against the Nodbc, if look at the Nodbc manual included
> in the NAV DVD you can find the following:
>
> "Important
> If you want to filter using a date range, you must use the
> SetFlowFilter predicate.
> However, when you use this predicate you can only specify one date
> range per filter
> and you therefore cannot set filters that specify more than one date
> range.
>
> The SetFlowFilter predicate is maintained for backwards compatibility
> and to
> support date ranges."
>
> So I do queries with SetFlowFilter in this format:
>
> pred SetFlowFilter, '<TableName>', '<FieldName>', '010101..310101'
>
> Hope this helps.
>
>
>
> Brett Haydon ha escrit:
> > Hi we are doing a 2 stage upgrade from 2.6 Native to 4.0SP2 Native then
> > converting to SQL 2005.
> >
> > Until we finally migrate the database to SQL 2005 we are stuck using some
> > existing Excel queries through the N/ODBC interface, but some of the
> > functionality from 2.6 seems to have been removed in 4.0.
> >
> > In v4 it doesn't seem possible to set a date range on a flow filter in
> > N/ODBC. If someone can prove me wrong and show me how this is done I'd be
> > most appreciative.
> >
> > I have managed to do a single date filter using {pred SetFlowFilterMultiple,
> > Item."Date Filter",21062007} which works but any variation on a date range
> > doesn't.
>
>
 | 
Pages: 1
Prev: Navision version 5.00 Job Queue
Next: Command Line Options for Navision 5.0 Setup