I can assure that it's not an Outlook problem. This is an issue that has
started to surface on isolated systems specifically with ContactGenie
Importer 1.3 and at this point we are still trying to locate what is common
among the systems being affected. We know the 3rd party component being used
that is experiencing the error (right down to the precise line of code) but
it's something that so far we have found impossible to replicate on any
combination of Windows / Outlook / input file types that we've tried nor can
any of our external testers get this error. Overall - the program works on
the majority of systems that it's being installed on which is why this is
really hard to track down.
While only being reported to us in very limited fashion relative to
downloads - this is right now our number one priority but it's only going
to be from people's feedback that we're going to be able to isolate the
cause. We can't even test alternatives since we can't get the problem to
happen in the first place so there is no way for us to know if anything we
try differently makes a difference.
So far the common thread is this:
- in all cases that we know of - a custom form is being used
- in all cases - CDO has not been installed on the system which we are
going to specifically check for in the next update but
that shouldn't have been mandatory for CGI (it is for DataPorter for
which we haven't seen this problem come up and it
uses the exact same component) - however, so far we do know that when
CDO was installed after the fact - the problem
still remained on at least one of the systems reporting back to us).
We are investigating whether "admin rights" are required for some reason
when this is being installed since it appears the component is not getting
registered properly. A new setup package is being uploaded to our website
sometime this evening in the off chance that something in the package has
become corrupted affecting "some systems".
If you haven't already done so - please contact us directly via our email
support address so we can get some information from you - right now we're
comparing as much information as people provide us to determine what the
common thread is among these systems. If you can send us a copy of the
custom form you are using - we will add this to the mix of tests on our
systems
to see if there is something within the form that is possibly triggering
this issue in conjunction with the 3rd party component we're using - so far
none of the custom forms we use to test with have failed and these include
many customer created forms.
Karl
__________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0
"Power contact importers for MS Outlook '2000/2003"
http://contactgenie.claxton.com