Has anybody designed there own lookup

[Dick Anderson]

What to do if you don�t like the way the lookup function works?

When the lookup window opens up I should be able to press a key on the keyboard; new data should appear in the window and I should be able to continue making key presses until what I�m looking for is highlighted. If it is not in the lookup table I can select new.

After I press the Enter key the lookup window should close and I should be returned to my entry form.

If the record was found the fields on the entry form will be filled and cannot be edited. If the record is new I can fill the record on my entry form. Once the record is saved it cannot be edited on my entry form.

What do I do? Put a button on my entry form and script my own lookup or use A5�s procedure but script intervention to change the operation?

[Lance Gurd]

when you have the lookup tab open on field rules tick the display as a drop down option, then try it. Typing will progressively find your record. Then the data entry tab can be used to define which fields can be accessed.

Lance

[Mike Wilson]

Mnay options

What to do if you don�t like the way the lookup function works?

When the lookup window opens up I should be able to press a key on the keyboard; new data should appear in the window and I should be able to continue making key presses until what I�m looking for is highlighted. If it is not in the lookup table I can select new.

After I press the Enter key the lookup window should close and I should be returned to my entry form.

If the record was found the fields on the entry form will be filled and cannot be edited. If the record is new I can fill the record on my entry form. Once the record is saved it cannot be edited on my entry form.

What do I do? Put a button on my entry form and script my own lookup or use A5�s procedure but script intervention to change the operation?

Dick,

The filed rule lookup offers a robust lookup process, but with dialog boxes and embedded browses on forms, you can generate elaorate look up actions with many custom filtering processes, and button-based responses. A simple one is attached.

Mike W

[Cheryl Lemire]

no attachment

Mike

I don't see any attachment :(

[Mike Wilson]

oops

Attached example:

[Dick Anderson]

Thanks Mike

I suppose the operation is run by the scripts I found on the form. That is; If I study the scripts, I too can recreate this type of lookup. Right?

Dick

[Mike Wilson]

one of many ways

Dick,

The example was just one of many ways to get to a lookup table. There are others. Yes, if you look at the scripting you can follow the process and get understanding of the steps to that example end. That's how many of us move forward.

If the record was found the fields on the entry form will be filled and cannot be edited. If the record is new I can fill the record on my entry form. Once the record is saved it cannot be edited on my entry form.

For this look to 'Disallow Edits'.

Look forward to helping as you might need.

Mike W

[Dick Anderson]

Thanks again Mike

I've been working with the example you sent me. I didn't notice before that it doesn't use a series of keystrokes. If I want to find "KEY" typing in KE might highlight "ENTRANCE". Also: When the list comes up in the list box it doesn't always start at the top of the list. If I type a letter that nothing in the list begins with, it won't even try to come close to finding a selection.

Is using keystrokes an intended part of the script or just something that happens?

Dick

[Tom Cone Jr]

Dick, to progressively narrow the search with each succeeding keystroke a different approach is required. Mike's is searching for the first letter, which is often all that's needed.

Suggest you click the Resources Link, visit the Newsletter Archive, and search for the article on Progressive Lookup. Jim Chapman did a couple of tutorials there which will show you how to create a "progressive lookup".

--- tom

[Dick Anderson]

Thank you everybody

I downloaded a tutorial from Alpha Software "using A5" by Jim Chapman which demonstrates a progressive lookup.

Dick

[Al Buchholz]

Dick

Look at the code archive to get a later version that is more efficient..

http://msgboard.alphasoftware.com/al...ad.php?t=57089

[Garry Flanigan]

Note that there is a slight problem with Jim's code as the last record is not displayed in the built list. The following section has an error:

function BuildList as c (vTable as p,vIndex as p,vCount as n)
	BuildList = ""
	for i = 1 to vCount
		vKey = vIndex.key_get()
		BuildList = BuildList + "{data="+padl(alltrim(str(vKey.record)),10,"0")+"}"+ vKey.key + crlf() 
		vTable.fetch_next()
		if vTable.eof(vIndex.name_get())
			exit for
		end if 
	next
end function

It should be:

function BuildList as c (vTable as p,vIndex as p,vCount as n)
	BuildList = ""
	for i = 1 to vCount
		vKey = vIndex.key_get()
		BuildList = BuildList + "{data="+padl(alltrim(str(vKey.record)),10,"0")+"}"+ vKey.key + crlf() 
		if vTable.eof(vIndex.name_get())
			exit for
		end if
vTable.fetch_next()
	next
end function

The vTable.fetch_next() is moved to the correct place. This is very easy to use. Refer to the article mentioned in the earlier post to get the entire code. Also, consider using the progressive lookup detailed in the A5V7 "Learning XDialog" sample application. It takes more work to set up but is more flexible and can show more columns.