>The Child Table (the one that when replaced with a local view works without an error) was set to .NULL. I replaced it with .T. and still get the same error.

There is no reason that you should get a problem of the type you describe because you use a table over a view. C5's often occur with index corruption and similar. Have you tried reindexing and packing the table for example? It might be that the view, creating a fresh cursor, avoids these issues. Whatever way you look at it, if this is part of a shipping application, you really need to find out exactly what is happening rather than just accept that it works one way and not another. Even if you end up using a view, maybe you should try re-indexing the table (delete and recreate the tag(s)) and try and get it working with the table.

As to your question, no, I dont think performance is an issue using a local view. If you want to use the view instead of the table for the child data, go right ahead with confidence. However, if I were you, I would want to get this working with the table because there is no reason why it shouldn't work. You may just hit this problem down the line so if you have the time, investigate it further.