Dave,
We are experiencing the same problem here. Unfortunately, I don't
believe it is a problem with Vantage per se, but rather an issue
between Crystal and Progress. That being said, I don't hold out a
whole lot of hope for Epicor coming up with a fix in the near term.
This is what we experience. If we have someone who runs a "canned"
vantage report (one for which a data definition exists, such as the
Job Traveller) which contains an ODBC subreport in it (because the
data I'm looking to print is not on a table available in the data
definition) -- then the user turns around and runs a report we
created from scratch (using only ODBC connections), it will hang
every time.
We get around this by either (a) CTRL-ALT-DEL when you forget and
run an ODBC report after a canned Vantage report, or (b) running two
instances of Vantage, and always running, for example,
Travellers/Packing Slips/etc from the first session, and our
customized ODBC reports from the second.
The "fix" to this is under version 8.03, you will have the ability
to create reports based upon dashboards or BAQ's (I don't recall
which one - perhaps both), and this will eliminate the
Crystal/Progress bug.
My suggestions is to report it to Tech Support. Perhaps enough of
these reported will trigger this raising to a higher level
priority. Our users who are running two sessions of Vantage to
eliminate lockups would love a fix.
Kevin Simon
We are experiencing the same problem here. Unfortunately, I don't
believe it is a problem with Vantage per se, but rather an issue
between Crystal and Progress. That being said, I don't hold out a
whole lot of hope for Epicor coming up with a fix in the near term.
This is what we experience. If we have someone who runs a "canned"
vantage report (one for which a data definition exists, such as the
Job Traveller) which contains an ODBC subreport in it (because the
data I'm looking to print is not on a table available in the data
definition) -- then the user turns around and runs a report we
created from scratch (using only ODBC connections), it will hang
every time.
We get around this by either (a) CTRL-ALT-DEL when you forget and
run an ODBC report after a canned Vantage report, or (b) running two
instances of Vantage, and always running, for example,
Travellers/Packing Slips/etc from the first session, and our
customized ODBC reports from the second.
The "fix" to this is under version 8.03, you will have the ability
to create reports based upon dashboards or BAQ's (I don't recall
which one - perhaps both), and this will eliminate the
Crystal/Progress bug.
My suggestions is to report it to Tech Support. Perhaps enough of
these reported will trigger this raising to a higher level
priority. Our users who are running two sessions of Vantage to
eliminate lockups would love a fix.
Kevin Simon
--- In vantage@yahoogroups.com, "Dave Olender" <dolender@...> wrote:
>
> We are having a problem with the Crystal Runtime XI R2 and I was
> wondering if anyone else has seen this.
>
> If I print a Crystal based form (like the job traveler) and then
try
> to run one of my custom ODBC reports, my Vantage session locks up
> and I have to manually end the Vantage session on my workstation.
>
> If I Print a Crystal based form (like the job traveler) and then
> print an OpenEdge based report (like the production detail) and
then
> print my custom ODBC report, then it works fine.
>
> I have submitted this as a problem on the Epicor site, however
they
> seem to be having trouble duplicating this behavior. Strangely, I
> am also doing some consulting work for a customer that is running
> Vista and they have the exact same problem. Note: I did not setup
> the ODBC clients at my customers.
>
> This leads me to beleive that this is a global problem and
> considering the number of custom Crystal forms we are using, it is
a
> Major headache.
>
> Any help would be greatly appreciated.
>
> Dave Olender 651-246-3281
> dolender@...
>