More like they aren't going to rebuild (as the build they have will work after 1st July...)

This is exactly what I needed. I absolutely should have remembered the good ol' dependency walker from yester-year. Just when COM was starting to be a vague memory, it came back and reminded me just how much trouble it can cause! Thanks!:-D If you continue to do the same things you always did, don't be surprised if you get the same results you always got.

all your base are belong to us

Marshall wrote: The web translator said: "For success one must aquire one's self" My translation based on the code: "If the copy of the this pointer is valid, return true. Damn, that is an awesome translation, spot on too. Maybe truth does lie in code... ;) Paul Watson Bluegrass Cape Town, South Africa Marshall wrote: The web translator said: "For success one must aquire one's self" My translation based on the code: "If the copy of the this pointer is valid, return true.

In case someone else has the same problem, here's what I came up with: :-O The best solution IMHO, is to install VMWare on your PC and load the Japanese versions of Windows and Visual Studio. The downside is the cost involved. The JP versions of the OS and VS are free to MSDN Universal subscribers, but VMWare is about US$300. A free workaround is to install all the JP & Asian fonts needed to support the kana used in your documents. There could be a dozen or more, depending on how they were written. Beware each one resides in run-time memory and slows the PC to a crawl.:( Then when opening EACH file, follow these EIGHT steps: Menu-File -> Open -> File -> Browse -> Open -> Open With -> Text Editor with Encoding -> Select from seven (!) Japanese code pages. Marshall If you continue to do the same things you always did, don't be surprised if you get the same results you always got.

Thanks! I appreciate you taking time to answer this. :) marshall If you continue to do the same things you always did, don't be surprised if you get the same results you always got.

They are putting Win2K SP3 together right now. They are also doing an unprecedented BETA with the XP SP1 with approx 10,000 testers if I remember correctly. Success is measured by ones ability to mask complexity with simplicity.

Just after posting, I discovered the problem. :-O I'm posting the solution here in hopes it will help someone else in the future. It turned out to be an authentication issue. Adding the following line to the Web.config file took care of it. (So far...) < identity impersonate="true" /> :) :) :)