Dick:

>Found the problem.

Thats great.

>As it turns out, that was just the tip of the iceberg. Apparently the whole .pjx table got corrupted somewhere along the way and the ProcFile just happened to be showing up at the head of the list.

Its hard trying to diagnose a problem remotely sometimes because you just can't account for things like corrupted project files <s>. However, at least you have a better idea of how the procedure files should be handled even if that wasn't the main issue. As I recall in V6, the framework uses a project-hook (or a proprietory project scan) to do things like acknowledge when a proc file or class library is added/removed from the project, and as a result updates the framework's meta-data (appreg02 etc). If the project is bad, it really doesn't stand a chance of doing the job correctly, particularly when trying to process data-driven features like the ones discussed.

>Thanks for all your help, Gary, I appreciate it.

No problem, glad to assist.

Best