Not sure what caused this, but the problem is this. We have a SELECT where we are using LE and GE. It's been working for several months internally. Today while backing up the application to another PC, someone try to enter some data. They got some message (I didn't see it), but I guessed it was just because the data/program files were being backed up. Whether this has anything to do with it or not I don't know, but I am providing this in case it might prove helpful. Now when a Select is perform the LE and GE are not behaving as they should.

For example, the original Select was:

Select FILENAME with startDate LE Today AND with endDate GE Today…

Now to make things work as before, we had to make the following adjustments, if we wanted to fine Today=115:

TodayLT=Today + 1 TodayGT=Today -1 Select FILENAME with startDate LT TodayLT AND with endDate GE TodayGT…

In doing a search I saw previous concerns with using the LE and GE. However, I would think that 1) they would have been fixed by now and 2) I can't understand how something could have worked earlier and then stopped (like today).

Any ideas on what might have caused the LE and GE to break and how to fixed this problem.

Thanks,

Ray Chan

Windows XP Professional

OI32, 4.13

Ray

This is VERY characteristic of an MV in a key value throwing indexes out by one. Write a quick program to scan ID fields for delimiters.

The Sprezzatura Group

World Leaders in all things RevSoft

Mr. Sprezz and/or the World,

I don't think that it is just a MV issue in a key field since we are seeing the LE and GE not working in other files as well.

We don't see any extraneous delimiters.

Does anyone have any other suggestions?

Thanks,

Ray

Ray,

From the Dept of Shots in the Dark:

Try = instead of LE and GE.

- Oystein -

What happens if you use between? (Which we recommend in any case for speed)

The Sprezzatura Group

World Leaders in all things RevSoft

Sprezzatura,

It's not a 'between' query. Is it?

- Oystein -

Oystein and Mr Sprezz:

First, regarding =,

I tried this and it does not work… the system is still treating = as ]

Two, regarding "between", I guess we could make this work, but we have to adjust the entered values. Briefly, we use "between" like LT and GT.

What I'm really concerned about is what happened to LE and GE? How did this "break" in our system? Like I said it was working, and now it's broke.

I will be out of pocket for the next several days, but should anyone (RTI, etc) have any ideas how to fix this and/or what caused this I would appreciate some help.

As usual, many thanks,

Ray Chan

It's a small possibility that SYSDICT got corrupted.

Check the entries for GE, LE, LT and GT and ensure that field 4 matches the key. Same for the , =, which should match the apporpriate 2 letter symbol.

It's probably not this, but worth the time to look.

The Sprezzatura Group

World Leaders in all Things RevSoft

Hello Ray,

I don't think you've told exactly what's wrong with your GE and LE - how the search results differ from the expected ones. You've only said that your GE and LE yield wrong results but GT and LT work OK.

Your query is not a BETWEEN kind of query. It is not possible to do

WITH BETWEEN AND

When Sprezzatura suggested using BETWEEN I assume they could have meant doing

BETWEEN AND

as a substitute for

GE

and similarly for LE. I.e, you would need two BETWEEN's in your query.

I'm not sure what it is you say about your use of BETWEEN. BETWEEN is like a combination of GE and LE, and not GT and LT. Do you say your BETWEEN yields wrong results too?

Cheers,

- Oystein -

View this thread on the forum...