Can't figure it

[Bruce MacPherson]

I created a small script to search for a keyword. I have one machine running A5v4 and one on A5V3 worked fine on both.
Had a crash and had to reinstall A5V4 on one and now it doesn't work on the A5V4 but does on A5V3
Tell me if you see something

''XBasic
dim jn as p
dim tsearch as c
tsearch=ui_get_text("Job Text Search Box","Enter the Search String")
if tsearch=""
end
end if
jn=table.open("job numbers",FILE_RW_SHARED)
update.fields = 1
update.field1 = "search"
update.expr1 = ".f."
jn.update()
jn.fetch_first()
while .not. jn.fetch_eof()
if like(tsearch,jn.job_name)
jn.change_begin()
jn.search=.t.
jn.change_end()
end if
jn.fetch_next()
end while

query.description = ""
query.order = ""
query.filter = "SEARCH=.T."
query.options = "I"
jn.query_create()
browse.view("jsb")

[Stan Mathews]

RE: Can't figure it

Your script looks fine.

Possible that you made other 'minor' changes? Like() is case sensitive, maybe you transformed job_name to uppercase?

[Bruce MacPherson]

RE: Can't figure it

The script listed was the cut and paste from the db.

I'M getting pretty grumpy.

[Stan Mathews]

RE: Can't figure it

I meant maybe you've changed the values in the job_name field to be transformed to uppercase, or proper first caps. Then if the tsearch variable was lower case, the search would fail.

Do you have two versions of your tables, one for V4 and one for V3, or one set of tables and an app in each version looking at the same tables?

[Bruce MacPherson]

RE: Can't figure it

Both are looking at the same tables.

A two computer network.

When I do the search it finds every record.

[Stan Mathews]

RE: Can't figure it

I don't have much knowledge of previous versions.

Two things:

query.options = "I"

I don't remember this and can't find it in the docs or readme file, options I see are M, N, X, D, U.

jn.query_create()

Examples all show as

indx = jn.query_create()

Wild guessing here, probably not much help. Finding all records sounds like nothing is happening with the query.

[whanigsberg]

RE: Can't figure it

Stan,

query.options = "I"

means case insensitive.

It's buried in some readme or someplace. I didn't know what if meant for the longest time.

Bill

[Peter.Greulich]

RE: Can't figure it

OK, I learned something today ("I"). What about M & X?

[Tom Cone Jr]

RE: Can't figure it

Bruce, I wasn't familiar with the tbl.update() method you use, so I read the manual. In vers. 4 this method requires exclusive use of the table according to the book. Don't know what vers. 3 needed, or whether this makes a difference.

If the same script ran fine under vers. 4 before your crash I'd begin thinking of a thorough scan disk, and possibly reinstalling vers. 4...

Hope these ideas help.

-- tom

[Stan Mathews]

RE: Can't figure it

Peter,

From the 403 readme

New Options for .Query_Create Method
Alpha Five now has two new option flags for the .query_create() method. These options are set with
the query.options variable. The options are:
query.options = "M"
If this option is specified, Alpha Five will build a new query list even though a) an existing query list exists,
and b) an existing Index exists (both of which, Alpha Five could have used rather than running a new
query).
query.options = "X"
If this option is specified, Alpha Five will use an index even if an existing query exists (which Alpha Five
would otherwise have used in preference to the index)
If no options are specified, then when you run a query, Alpha Five does the following:
a) if the same query has been previously run, use that query list.
b) if not, but if an index that satisfies the query criteria exists, use the index.
c) if a previously run query does not exist, and if no index exists, run a new query.
Previously, Alpha Five only offered one option, �N�, which caused Alpha Five to run a query, rather than
selecting an index, if an index would have satisfied the query criteria.
If you want to trade off speed for certainty that your applications will run correctly, you should consider
using the �M� option in your Xbasic code. (In most applications the speed difference will probably not even
be noticeable.) This ensures that whenever you use the query_create() method, Alpha Five is creating a new
query from scratch, and not relying on a previously run query, or an index, that could be corrupt.
For example:
Tbl = table.open(�customer�)
Query.filter = �state = �ma��
Query.order = �lastname�
Query.options = �M�
Indx = tbl.query_create()


And thanks yet again to Bill.

Stan

[JerryBrightbill]

RE: Can't figure it

Bruce,
Looking at your script, I see a number of possible problems. When I tried it with a test table, it found no records and both the update and query failed. The first problem is that you are fetching thru the table twice, first with the update and then the fetch itself. This could slow the search greatly on large tables. The second is that you do not specify and index at the start of the script and therefore whatever index or query is in effect when the script runs will determine what records are searched. If a query exists at the start, only the records in that query will be updated and fetched. The third problem is with the variable used in the LIKE expression. Like is case sensitive, so it would be a good idea to change both the field value and the variable to trimmed, lower or upper case.

In any case, here is a modified script that I tested with a test table with dummy data and it worked even if I specified a wildcard in the search criteria.

dim jn as p
dim tsearch as c
tsearch=alltrim(lower(ui_get_text("Job Text Search Box","Enter the Search String")))
if tsearch=""
end
end if

jn=table.open("job numbers",FILE_RW_SHARED)
idx = jn.index_primary_put()'/// Sets index to recno order

count = 0
jn.fetch_first()
while .not. jn.fetch_eof()
jn.change_begin()
if like(tsearch,alltrim(lower(jn.job_name) ))
jn.search=.t.
count = count + 1
else
jn.search=.f.
end if
jn.change_end()
jn.fetch_next()
end while

if count = 0
jn.close()
ui_msg_box("Search","No records found that meet search criteria",UI_ATTENTION_SYMBOL)
end
end if
query.description = ""
query.order = ""
query.filter = "SEARCH=.T."
jn.query_create()
browse.view("jsb")

end

I found the if statement to kick out of the script if no records were found to be necessary. If no records were found, the browse would open in enter mode.

Jerry

[Bruce MacPherson]

RE: Can't figure it

Jerry,
I tried the script as you had it.

If I use straight text it will never find a record.

If I add a wildcard in any position of the search it pulls every record.

I ran the script as it was before, and then ran a query to search for records with a .T. in the search field. It pulled up exactlly the correct fields. Therefore the search is correct but the query list is the root of the problem.
Any suggestions?

Bruce

[Michael Humby]

RE: Can't figure it

Where has all this query information come from. I have spent the last few weeks trying to force new queries with the 'N' option with no success. Where is the info describing the further options.

The documentation that I have read only gives three options but it does say that a query can have one or more options. How does one force more than one option? Would it be

query.options="N,D" or

query.options="ND" without a comma

Any help appreciated

Michael

[Stan Mathews]

RE: Can't figure it

From the 403 readme

New Options for .Query_Create Method
Alpha Five now has two new option flags for the .query_create() method. These options are set with
the query.options variable. The options are:
query.options = "M"
If this option is specified, Alpha Five will build a new query list even though a) an existing query list exists,
and b) an existing Index exists (both of which, Alpha Five could have used rather than running a new
query).
query.options = "X"
If this option is specified, Alpha Five will use an index even if an existing query exists (which Alpha Five
would otherwise have used in preference to the index)
If no options are specified, then when you run a query, Alpha Five does the following:
a) if the same query has been previously run, use that query list.
b) if not, but if an index that satisfies the query criteria exists, use the index.
c) if a previously run query does not exist, and if no index exists, run a new query.
Previously, Alpha Five only offered one option, �N�, which caused Alpha Five to run a query, rather than
selecting an index, if an index would have satisfied the query criteria.
If you want to trade off speed for certainty that your applications will run correctly, you should consider
using the �M� option in your Xbasic code. (In most applications the speed difference will probably not even
be noticeable.) This ensures that whenever you use the query_create() method, Alpha Five is creating a new
query from scratch, and not relying on a previously run query, or an index, that could be corrupt.
For example:
Tbl = table.open(�customer�)
Query.filter = �state = �ma��
Query.order = �lastname�
Query.options = �M�
Indx = tbl.query_create()

[Peter.Greulich]

RE: Can't figure it

Thanks Stan