I'm using a variety of Decision Components on a form (Decision Grid/Chart/Query/Source) to enable users to obtain different views of reported data. The data is on an Oracle 7.3 Db on an NT4 server and I'm using D6 Enterprise.
I have the form set up to display test data at design time, which it does with no problems.
However, when I try to test the form in run-time mode I always get the following message;
"Project raised exception class EComponentError with message 'A component named Series 1 already exists'. Process stopped. Use Step or Run to continue."
If I then delete the offending Chart and re-run the form I get a Db error reporting unknown userid or password (no login prompt, although this is set to be required).
So, it seems I have TWO problems - one with TDecisionGraph and one with DecisionQuery!
The project DOES display the standard login prompt on initially being opened in design-mode.
This is the first time I've used the Decision Support Components - I used them as a big pitch in persuading my boss to buy Delphi in the first place (Corporately, we're standardised on MS VB). Although the people upstairs are very happy with the Db work we've produced with Delphi the use of the Decision Support Components in an app. which can be distributed to non-technical managers is an absolute pre-requisite.
HELP!
I have the form set up to display test data at design time, which it does with no problems.
However, when I try to test the form in run-time mode I always get the following message;
"Project raised exception class EComponentError with message 'A component named Series 1 already exists'. Process stopped. Use Step or Run to continue."
If I then delete the offending Chart and re-run the form I get a Db error reporting unknown userid or password (no login prompt, although this is set to be required).
So, it seems I have TWO problems - one with TDecisionGraph and one with DecisionQuery!
The project DOES display the standard login prompt on initially being opened in design-mode.
This is the first time I've used the Decision Support Components - I used them as a big pitch in persuading my boss to buy Delphi in the first place (Corporately, we're standardised on MS VB). Although the people upstairs are very happy with the Db work we've produced with Delphi the use of the Decision Support Components in an app. which can be distributed to non-technical managers is an absolute pre-requisite.
HELP!