All I can think of is that two different dll's are being used. One distribution dll which is only used by crystal at this point and one development dll which is the one being used by vb. It could be that the dev dll is faulty.