It approached 8 GB, and that crashed Windows. I had trouble getting to the Task Manager, but when I did, I found that BricsCAD was gobbling up enormous amounts of memory, and that memory usage was steadily rising. I proceded to make the edit, and BricsCAD promptly froze. The command appeared to complete without a problem. I applied the 'Switch to Local' command to eliminate the use of XREF's. I decided not to risk corruption of the component paths again. I returned to the original assembly, opened the assembly browser, and corrected the paths. I tried other assembly files stored in other network folders with their own XREF subfolders. When I opened the file, I discovered that a few of the dozen or more XREF's were flagged as 'not found', or their paths were no longer correct.

Recently I had to make a minor edit to one of these assemblies. In each case, all the XREFS were in a subfolder of the network folder where the assembly file resided. I have a half dozen assembly files I've created over the past several years.