well, there are more underlying problems. the network admin was able to rename the dll using his login. Windows automatically recovered the dll and the size and version look ok. I am still getting the same error though, so another dll must be corrupt. I am still searching and hoping I will find the answer. i appreciate any help or any ideas.
Randy Belcher
AFG Industries, Inc.