By a process of elimination I tracked down the following line in my form init code:

"thisform.grid1.recordsource=dbase"

as being the trigger point for the error below.

error: "property POPINDEX1 does not exist"

The error is handled outside the default error handling routine (i.e. instead of the default error handler with its "Cancel Suspend Ignore Help" options it just pops up in a dialogue box with "OK" and "Help" options - I suspect this is a clue but I don't know how to interpret it)

Popindex1 is a parameter passed to the form. Its name, in this particular situation is "callprime". The recordsource parameter (dbase) is "accountcalls" - a parameterised view. Both variables and their related properties are alive and well at the time of the "error" and there is no connection between them relevant at that point in the code. The view is open and indexed. Furthermore, if I just acknowledge the error, the code continues and performs exactly as it should. This includes setting the order of (dbase) to the index held in the allegedly non-existent property (popindex1).

It occurs to me that its possible that the code effectively "opens" the view again despite the fact that its already open and indexed. If so, then, as with all views, there are no indexes in operation and the error message might be pointing to that problem.

Can anyone confirm that this is standard behaviour when allocating a view as a grid.recordsource? If so, where is it documented and how do we get around it? If not, can anyone clarify what else may be happening and what I might be able to do about it.

Thanks