Crystal Reports 10.0 compatibilty issues !

Hi

I have to upgrade the reports my project (VB 6.0 and MS-SQL 2000) from crystal reports 8.5 to crystal reports 10.0, but I checked that crystal reports 10.0 does not support OCX method.

I want to know

1) Will my existing VB 6.0 code support the new crystal reports 10.0 or will I have to make any significant changes in the code ?

2) Do I have to change the report files or will they work fine with crystal reports 10.0 ?

3) If I save my existing report in crytal report 10.0, then will I be able to open it again in crystal report 8.5 ?

OR can anyone suggest me a site where I can get answers to the above questionsHello !!!

Can anyone help me pleeeease !!!!|||Hi,
try in this site
http://support.businessobjects.com/search/default.asp

u can get the info
just type the required issue u want in search u may get the info

thanks
manosql

crystal report compatability

The company that I am working for is looking to make the upgrade to 2005 from 2000, and we will need to continue to use crystal reports 8.5 until we have everything ported into the 2005 reporting services.

Does sql server 2005 support crystal reports 8.5?

Thanks

Moving to "SQL Server Reporting Services", which has a better chance answering this.

Crystal 8.5 Page Length less than 4"

Hi!

I have a VB 6.0/CR 8.5 official receipt printing on a form that is 8.5 x 3.5. It was running perfectly under Windows 98 but when I have upgrade to Windows XP I can no longer access withing CR 8.5 forms that are less than 4 inches. Any idea how can I resolve this issue.

Thanks.

rclazarito[ Thread moved to Crystal Report ]

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
> > >
> > >
> >
> >
>