Sorry, I didn't research this like I'd like to before posting, but maybe
someone can point me in the right direction.

Why would a (charater or other) field that has always been searchable
suddenly become not searchable? This seems to be happening only on fields
that are populated when a table on the form is refreshed. Instead of
calling up matching records, you get the generic Remedy message saying
nothing there was no match (even though there are records that do match
what you're trying to query). According to our users, we were definitely
able to search on these fields & have been doing so for a long time.

The only thing I can think might have precipitated this was me adding other
fields to the form. There's no workflow at all associated with what I
added (they're simply there for manual data entry). I deleted the new
fields I added, but this doesn't fix the problem.

Any ideas?
Thanks,
David Durling
UCNS Help Desk
University of Georgia

ARS 4.0.2
Oracle 7.3.4
Solaris 2.6
ARWeb 4.0

_____________________________

Hi

I'd suggest you take a workflow (Active Link [AL] log) while searching this
field. If I have understood you right, you are having a problem when you
query by example, i.e. you enter a value to that field when in a Search
mode, and search, you get a no match error although there are some records
there that match the condition.

What I suspect is happening, is that some of your AL's are setting some
value in certain other fields (visible or hidden) at the time of searching,
and this must be not matching your search criteria.

Even if my above assumption is not true, a AL log (workflow log) together
with an SQL log may prove useful.

My 2 cents.


Joe DeSouza
CyberMAK Information Systems,
Kuwait.
Mobile : +965 940 6129.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of David Durling
Sent: Friday, September 07, 2001 9:31 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: field suddenly not searchable


**

Sorry, I didn't research this like I'd like to before posting, but maybe
someone can point me in the right direction.

Why would a (charater or other) field that has always been searchable
suddenly become not searchable? This seems to be happening only on fields
that are populated when a table on the form is refreshed. Instead of
calling up matching records, you get the generic Remedy message saying
nothing there was no match (even though there are records that do match
what you're trying to query). According to our users, we were definitely
able to search on these fields & have been doing so for a long time.

The only thing I can think might have precipitated this was me adding other
fields to the form. There's no workflow at all associated with what I
added (they're simply there for manual data entry). I deleted the new
fields I added, but this doesn't fix the problem.

Any ideas?
Thanks,
David Durling
UCNS Help Desk
University of Georgia

ARS 4.0.2
Oracle 7.3.4
Solaris 2.6
ARWeb 4.0

________________
_____________


You may also control your subscription options, including UNSUBSCRIBE, at
www.ARSLIST.org

_____________________________

David,

Do you have any hidden fields on the forms that have fields set to some
default values? This could be the reason why your not getting any results
for your search even if the criteria your specifying should return some
results. What I would recommend is to do a Ctrl+E first, then type or select
the criteria you want to search on and see if this returns any results.

Hope this is useful.

Regards,

Saby

----- Original Message -----
From: "David Durling"
To:
Sent: Friday, September 07, 2001 10:31 PM
Subject: field suddenly not searchable


> **
>
> Sorry, I didn't research this like I'd like to before posting, but maybe
> someone can point me in the right direction.
>
> Why would a (charater or other) field that has always been searchable
> suddenly become not searchable? This seems to be happening only on fields
> that are populated when a table on the form is refreshed. Instead of
> calling up matching records, you get the generic Remedy message saying
> nothing there was no match (even though there are records that do match
> what you're trying to query). According to our users, we were definitely
> able to search on these fields & have been doing so for a long time.
>
> The only thing I can think might have precipitated this was me adding
other
> fields to the form. There's no workflow at all associated with what I
> added (they're simply there for manual data entry). I deleted the new
> fields I added, but this doesn't fix the problem.
>
> Any ideas?
> Thanks,
> David Durling
> UCNS Help Desk
> University of Georgia
>
> ARS 4.0.2
> Oracle 7.3.4
> Solaris 2.6
> ARWeb 4.0
>
>
________________
_____________
>

> You may also control your subscription options, including UNSUBSCRIBE, at
www.ARSLIST.org


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_____________________________

Thanks to Joe & Sabyson for responding- it turns out that the problem the
user reported was not a problem, and was nothing new, after all. They are
trying to search a field that's designed to be populated on a table refresh
(the data coming from another form), so it make sense that they should get
no matching records.
Thanks for the trouble.

David D.


On Sat, 8 Sep 2001 10:20:06 +0400, Sabyson Fernandes
wrote:

>**
>
>David,
>
>Do you have any hidden fields on the forms that have fields set to some
>default values? This could be the reason why your not getting any results
>for your search even if the criteria your specifying should return some
>results. What I would recommend is to do a Ctrl+E first, then type or
select
>the criteria you want to search on and see if this returns any results.
>
>Hope this is useful.
>
>Regards,
>
>Saby
>
>----- Original Message -----
>From: "David Durling"
>To:
>Sent: Friday, September 07, 2001 10:31 PM
>Subject: field suddenly not searchable
>
>
>> **
>>
>> Sorry, I didn't research this like I'd like to before posting, but maybe
>> someone can point me in the right direction.
>>
>> Why would a (charater or other) field that has always been searchable
>> suddenly become not searchable? This seems to be happening only on
fields
>> that are populated when a table on the form is refreshed. Instead of
>> calling up matching records, you get the generic Remedy message saying
>> nothing there was no match (even though there are records that do match
>> what you're trying to query). According to our users, we were definitely
>> able to search on these fields & have been doing so for a long time.
>>
>> The only thing I can think might have precipitated this was me adding
>other
>> fields to the form. There's no workflow at all associated with what I
>> added (they're simply there for manual data entry). I deleted the new
>> fields I added, but this doesn't fix the problem.
>>
>> Any ideas?
>> Thanks,
>> David Durling
>> UCNS Help Desk
>> University of Georgia
>>
>> ARS 4.0.2
>> Oracle 7.3.4
>> Solaris 2.6
>> ARWeb 4.0

_____________________________