Thanks for help.

I discovered that event though the VCX will bloat while editting, that building the project performs a pack on the VCX files.

I think I found the source of my problem. The problem is nopt in VFP, but in the OS, or network settings. When I run the my tool on a stand-alone Win2Kpro machine, it works as designed. But when the tool is ran on a workstation accessing the classes through a mapped drive, the problem appears. It appears that the issue is in the caching of the write data. When I edit the class's method, then save the changes, the data is queued for write. But then when I attempt to read the class as a table, the OS is read directly from the VCX, and not from the cache. The CLEAR ALL appears to force the write cache to be writen to disk. Perhapes there is a API call I can use to insure the changes make it to disk before I attempt to read it as a table.

As to the other question regaurding what I am attempt to do. Well, in part, as a small part of the tool I am writing, the user can modify one of a series of methods, then after they save and close the class designer, the methods of the VCX are scan for specfic changes. This is where I discovered my problem. I would like to be more specific, but can not right now.