Select by Indexed Dates

[JD Kromkowski]

It does not appear that selecting by an indexed date actually works. If I use select by value (“?”). It does not matter whether I am in record view or form view. It also seems that trying to add a date index or even modifying a date index leads to a shut down.

[Michael]

On 09/11/2010 14:26, JDK wrote:
> It does not appear that selecting by an indexed date actually works.
>
> If I use select by value ("?"). It does not matter whether I am in
> record view or form view.
>
> It also seems that trying to add a date index or even modifying a
> date index leads to a shut down.
>

That is strange, but I have just looked and none of the tables I
typically work with have date indexes. I will set up a test tomorrow and
have a look.

Ciao, Neil

[JD Kromkowski]

This still appears to not work as one would think.

1. Open a form with a date index.

2. Choose the date field as the index.

3. Use the select record ("?")

4. Put in a date like "1/1/2010".

You might as well be searching with the "0" that is there as a default.

Upon further examination it looks like you have to (in you head, I guess)
change
"1/1/2010" to 733672.

But I am not exactly sure that using the Julian number actually is doing
it correctly. But although 733672 is "1/1/2010" I get taken to a record
with the date of "12/22/2009", which I presume means that I need the
Gregorian number.

In either case, surely the way this should work is that when selecting a
record by a date index, anyone should be able to put in date (1/1/2010 or
Jan 1, 2010) and get the right record.

[Michael]

On 13/05/2011 19:49, JDK wrote:
> This still appears to not work as one would think.
>
> 1. Open a form with a date index.
>
> 2. Choose the date field as the index.
>
> 3. Use the select record ("?")
>
> 4. Put in a date like "1/1/2010".
>
> You might as well be searching with the "0" that is there as a
> default.
>
> Upon further examination it looks like you have to (in you head, I
> guess) change "1/1/2010" to 733672.
>
> But I am not exactly sure that using the Julian number actually is
> doing it correctly. But although 733672 is "1/1/2010" I get taken to
> a record with the date of "12/22/2009", which I presume means that I
> need the Gregorian number.
>
> In either case, surely the way this should work is that when
> selecting a record by a date index, anyone should be able to put in
> date (1/1/2010 or Jan 1, 2010) and get the right record.
>

Hi John,

You are quite right. I only recently noticed this problem in a
commercial application that I was writing. I resolved it there, but that
has not yet gotten into SIMPOL Personal. I will put it in this week.

Ciao, Neil

[Author]

Posts