What is really kicking me in the head though?
It runs perfectly on Vista Ultimate, and gives me grief on XP!
I'll post a package in a few days when I finish it out.
That batch routine has been an awesome crutch, I have to thank Tim for it again!
So far it has allowed me to actually gain on general labor and productivity issues with client file handling.
We have had a great deal of grief with 2008 MEP and version conflicts.
The most honest thing I can say is that projects are being handled as CAD files so AEC removal has become a major crutch as well. Getting ADT 2005 projects has resulted in strange bug entity points being generated miles away from origin in the Z-Axis. So I AEC Export after setting all points in the Z axis to 0.
The major drawback to the routines is it replaces the initial Drawing1.dwg in memory on XP but doesn't in Vista. When this happens, every close of a file is trying to unload the menus and compile the cui/mnl files. Slows the entire process badly due to ABS.cui and all of our general customizations. I beleive it is a bug using the MdiTab17.arx file with 2008. If I do a new file from a template it stalls. So before I run the routine I have to open a qnew Drawing2.dwg. It sort of works....
I've been testing and refining for handling a more or less general formatting system to remove some guesswork and production failures by using some sugar for my users and taking the manual tasks out for a change.
The 2008 MEP Unreconciled Layers (bug/feature - who uses it?) issue is a major drawback but the batching utility lets me at least have a viable workaround. The work around let me apply more general formatting to try and smooth out the project work flow for the office. If I can actually get a few months out of it, I would be happy.