Crystal reports with java

Hello all,
I am new with Crystal Reports.
I have strange problems.
I created report with parameters and run it from Tomcat.

When i use default parameters window - parameters value which i add don't affect on report result - it uses previous parameters.
If i use custome jsp and add parameters programmatically it's work.

When i try to perform "Search for text" with some text i get:
"ERROR Some parameters are missing values".
If i leave search control empty and perform "Search for text" all work fine - i get parameters window and after this i get report.

Thanks in advance, VitalyWhen assigning value to the parameter make sure you spelled the name correctly and send the proper data that matches to the parameter datatype

Crystal Report to Default Printer

Hi,
We're writing in Crystal 8.5 and I'd like to know how to direct a report to a user's default printer. A report can be distributed to several locations or printers.
Thanks in advanceYou can make use of CR's printer collection
CR.printer='PrinterName'

Crystal Report Issues

hi,
I want to align the Subreport to the left. By default It is displaying the data in the right side of the main report. Is it feasible to align this to the left?.
Thanks
Vadivelan.plz. reply soon|||Assuming you have the subreport box on the left of the main report, wouldn't this depend on the alignment of the data within the subreport itself?

CRPEAUTO : Set default Printer

Ciao, i'm using VB6 and i need to set my report with the default printer then i can printout it.
How can I do this?
I'm using automation code and i need to do that using the same code.
Could you help me, please? It's very urgent and important.
ThanksSolution:

crystalreport.SelectPrinter "", "", ""

Ciao :-)

Cross database transactions.

Are Cross database transactions enabled by default? Not cross-server,
just cross database. If not what setting should I be looking at?Hi Frank
There is nothing special you need to do to enable cross database
transactions. Just make sure you have the necessary rights to the objects in
both databases.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"Frank Rizzo" <none@.none.com> wrote in message
news:%238lZ7g24HHA.4964@.TK2MSFTNGP06.phx.gbl...
> Are Cross database transactions enabled by default? Not cross-server,
> just cross database. If not what setting should I be looking at?

Cross database ownership chaining question

Do we need to worry about the default SP3 service pack upgrade which has
cross database ownership chaining disabled of all our objects on all
databases are owned by dbo.Using SQL 2000The cross-database ownership chaining option is only needed if you have
cross-database object references and users don't have permissions on the
referenced objects. If you have problems after disabling this option, you
can either turn it on selectively in the databases involved or grant direct
permissions on the referenced objects.
Note that your databases are not owned by 'dbo' - databases are owned by
logins (e'g' 'sa'). In order to maintain an unbroken cross-database
ownership chain for dbo-owned objects, the databases involved must be owned
by the same login.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> Do we need to worry about the default SP3 service pack upgrade which has
> cross database ownership chaining disabled of all our objects on all
> databases are owned by dbo.Using SQL 2000
>|||Is there some scripts that I can download to demonstrate this ?
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:e3iiH5myDHA.1744@.TK2MSFTNGP12.phx.gbl...
> The cross-database ownership chaining option is only needed if you have
> cross-database object references and users don't have permissions on the
> referenced objects. If you have problems after disabling this option, you
> can either turn it on selectively in the databases involved or grant
direct
> permissions on the referenced objects.
> Note that your databases are not owned by 'dbo' - databases are owned by
> logins (e'g' 'sa'). In order to maintain an unbroken cross-database
> ownership chain for dbo-owned objects, the databases involved must be
owned
> by the same login.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> > Do we need to worry about the default SP3 service pack upgrade which has
> > cross database ownership chaining disabled of all our objects on all
> > databases are owned by dbo.Using SQL 2000
> >
> >
>|||This KB article contains some scripts:
http://support.microsoft.com/default.aspx?scid=kb;en-us;272424&Product=sql2k
There is more info about cross db ownership chaining here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;810474&Product=sql2k
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:u6#BmQqyDHA.540@.tk2msftngp13.phx.gbl...
> Is there some scripts that I can download to demonstrate this ?
> "Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
> news:e3iiH5myDHA.1744@.TK2MSFTNGP12.phx.gbl...
> > The cross-database ownership chaining option is only needed if you have
> > cross-database object references and users don't have permissions on the
> > referenced objects. If you have problems after disabling this option,
you
> > can either turn it on selectively in the databases involved or grant
> direct
> > permissions on the referenced objects.
> >
> > Note that your databases are not owned by 'dbo' - databases are owned by
> > logins (e'g' 'sa'). In order to maintain an unbroken cross-database
> > ownership chain for dbo-owned objects, the databases involved must be
> owned
> > by the same login.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:eG1vClmyDHA.2156@.TK2MSFTNGP09.phx.gbl...
> > > Do we need to worry about the default SP3 service pack upgrade which
has
> > > cross database ownership chaining disabled of all our objects on all
> > > databases are owned by dbo.Using SQL 2000
> > >
> > >
> >
> >
>