I am trying to do something like the following...

SELECT * FROM Estimates WHERE  CURRENT_DATE <= (EstimateDate  + 90))

but I am getting an error msg.  Basically I want to add 90 days to the date
field stored in my table and make sure it is <= the current date.

Thanks

Scott


I did manage to figure this one out for someone a while ago in these ngs. Basically its because ELevateDB is standards compliant (or something like that)

I think its something like

SELECT * FROM Estimates WHERE  CURRENT_DATE <= DATE (EstimateDate  + INTERVAL '90' DAY))


Roy Lambert

Excellent - thanks!

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:1FA82560-DC3A-439C-B5A0-103AD35E8F6C@news.elevatesoft.com...
> Scott
>
>
> I did manage to figure this one out for someone a while ago in these ngs.
> Basically its because ELevateDB is standards compliant (or something like
> that)
>
> I think its something like
>
> SELECT * FROM Estimates WHERE CURRENT_DATE <= DATE (EstimateDate +
> INTERVAL '90' DAY))
>
>
> Roy Lambert
>

Here is the format that works (in case anyone searches for this in the
future):

"SELECT * FROM Estimates WHERE (CURRENT_DATE <= (EstimateDate + INTERVAL
'90' DAY))"


Thanks Roy for the help!

Scott

I'm sure we'll all get used to it .... eventually.

<rant>
I've spent a lot of today re-writing my logon system for my app. I'm nearly there. For starters the logic is reversed - the old logic went - first find the database, open users and then check logon info. Now it goes - try and login, then choose the database. Its bloody amazing just how much I'm having to alter. Memory tables are an especial pain in the bum. Before I could just create and open. Now I have to logon first then open the memory database hen I can create and open the tables. I've also had to alter the closing of memory tables for when the user aborted the logon.
</rant>

Roy Lambert