Import Visual Basic Project ... (Error)

[NewsArchive]

I am using the evaluation copy of Install Shield for Windows Installer that
I received at Microsoft Dev Days '99. I am attempting to use the Visual
Basic Wizard to import some projects. Several imported no problem, but two
of them are giving me an error. The error message reads:

There was an error encountered in scanning your project. Please make sure
the file you have specified is a valid VBP file (VBG files are not currently
supported).

It happens when the Visual Basic Wizard is displaying a progress bar
labeled: "Sorting Required Files by Destination ..."

Any ideas what is peculiar about my projects that might cause this? (One
thing that distinguishes both projects from the other successful ones is
that they contain ADO access to Jet databases and Data Environment
designers. Anything peculiar about the dependencies they would generate?)

Regards,
Tom

[NewsArchive]

This is actually a symptom of a known error when using the Crystal Reports
Control. Please check to see if these projects contain Crystal Reports
controls. If they do not, then we may be experiencing a similar error with
other types of controls that we would need to identify. If this is the case
we will need to take this offlined and then post a resolution when we find
one.

--
David Thornley
Lead Developer Support Engineer
InstallShield Software Corporation
http://www.installshield.com



Tom Smellie wrote in message <37ebd60b.0@news.installshield.com>...
>I am using the evaluation copy of Install Shield for Windows Installer that
>I received at Microsoft Dev Days '99. I am attempting to use the Visual
>Basic Wizard to import some projects. Several imported no problem, but two
>of them are giving me an error. The error message reads:
>
> There was an error encountered in scanning your project. Please make sure
>the file you have specified is a valid VBP file (VBG files are not
currently
>supported).
>
>It happens when the Visual Basic Wizard is displaying a progress bar
>labeled: "Sorting Required Files by Destination ..."
>
>Any ideas what is peculiar about my projects that might cause this? (One
>thing that distinguishes both projects from the other successful ones is
>that they contain ADO access to Jet databases and Data Environment
>designers. Anything peculiar about the dependencies they would generate?)
>
>Regards,
>Tom
>
>

[NewsArchive]

We are not using Crystal Reports in these projects. We are using some
other
third party controls though. I'll have to examine it and see if these
controls are used in the projects that are loading correctly. In the
mean
time, can you direct me to some details on the known bug?

Regards,
Tom

[NewsArchive]

The issue with Crystal occurs when we scan the file for its dependencies,
To track this down I hacked into the VBS and started removing references out
of the VB project until the scan worked. Then I created a simple project
with just the single reference to see if the scan still failed. Not pretty,
but I found the offending object in like 10 minutes.

--
David Thornley
Lead Developer Support Engineer
InstallShield Software Corporation
http://www.installshield.com



Tom Smellie wrote in message <37f12545.0@news.installshield.com>...
>We are not using Crystal Reports in these projects. We are using some
>other
>third party controls though. I'll have to examine it and see if these
>controls are used in the projects that are loading correctly. In the
>mean
>time, can you direct me to some details on the known bug?
>
>Regards,
>Tom
>
>

[NewsArchive]

David,

FYI, I am also having this problem with the Microsoft ADO Data Control
(msadodc.ocx, Version 6.00.8418). To be sure, I created a sample project with
this being the only control and got the same error.

Do you wish to know of any further instances should we encounter them?

Jason Dick

In article <37f28592.0@news.installshield.com>, "David Thornley"
<NoReplyPlease@installshield.com> wrote:
>The issue with Crystal occurs when we scan the file for its dependencies,
>To track this down I hacked into the VBS and started removing references out
>of the VB project until the scan worked. Then I created a simple project
>with just the single reference to see if the scan still failed. Not pretty,
>but I found the offending object in like 10 minutes.
>