Richie_S, I am glad it helped! As old as it is, this issue still plagues us all today. I had long forgotten about this issue until I recently updated to CCW 12.0 and then worked on a PanelView Standard (using PB32). Oh, the pain.
Thankfully, I had kept the DTL32.DLL_OLD file in my SysWOW64 folder and was able to overwrite the nonsense file from Rockwell. I strongly advise you all keep a copy for situations like mine (which I believe I mentioned in my original post).
drbitboy, I agree with you completely. As a single example, consider the quality of manuals, for example, between the PLC5 series and anything that has been released in the last few years. The old manuals were so information-rich that they would advise and teach the reader on subjects far beyond the scope of the PLC (although related). The quality was remarkable. The current crop of "manuals" are far too simplified and often times, silly (at least with regards to CCW and the the Micro800 series of PLCs). Then, there is the "legacy support" bit of their pricing scheme. You have to pay a premium for the chance to even think about talking to someone regarding older PLCs, drives, HMIs, etc. Come on!
Now, to (possibly) answer your question, DTL32.dll is called upon by WinPFTv2.exe (the file transfer utility for PB32). It seems to be referenced only in the Windows system folder (SysWOW64 for 64-bit systems and system32 for 32-bit systems, so a copy in the Panel Builder folder
may not work, but I think I will try it out one day for the heck of it. If it does work, it could help alleviate the headaches after upgrading other software. It is worth a shot, at least.