Thanks for the insight. There is nothing in the app elsewhere with the same name, but I'll give it a shot anyway. What is strange is that it only occurs when a subsequent search is done following a successful search. I was sure it had something to do with the code in the m.action button valid for a successful search. It also only occurs when the popup is selected. If I do a 2nd successful search and stay on the same control and manually tab into the popup, I receive the same error. I can tell that the correct table exists (addsrch) and it has records in it, but for some reason the popup's data source doesn't think so...and why on the 2nd search or subsequent sucessful searches only? Hmmmm, I was positive I had code that needed to be fixed. This spr has worked for 10 years in DOS and it is being run in VFP now and has this problem. We never noticed it in VFP before people seldom do two successful searches. They typically select a record after a successful search and close the form...

>Hi Tracy,
>
>I haven't checked your code, but I am momentarily shooting
>from baaad expieriences:
>
>VFP has problems identifying the correct function to run if
>functions have the same name stub and many app's are searched.
>
>examples:
>
>myscreen.prg
>myscreen.spr
>function myscreen() anywhere in another program file.
>
>try renaming the generated spr to a function name stub
>definitely not used anywhere in your program
>and call that new name, build the app and run.
>
>If the problem is gone, you will have some more work to
>do: perhaps we can coordinate a bit, since I have to recheck
>a few of my observations / assumptions.
>
>HTH
>
>thomas