Difference between supress and hide

When we write ckick on the crystal report-insert-section we will have several option to choose but what is the difference between Hide(Driil=Down ok) and Supress(No Drill-Down)??
I tried the help but I did'nt get the idea...good question!!! I've already search that but still no answer. They are the same in function, the only difference is the group tree when you view the report.|||I thought the help was quite clear - suppress if you don't want it at all, hide if you don't want it displayed initially but do want to be able to click on the item in the group tree and see the data therein.|||Ok,Igot the point:
if ur secton detail is between a group header and a group footer ,when u hide the section detail at run time if u double-click a ligne u will have the detail but if u supressed u will not have the detail,,try it u will understand better....

Diagram Tool Causes Strange Write Table Behavior

Using SQL Server 2000...
I'm creating a series of database diagrams for a database that has
~ 200 tables. The tables are segmented by module, so instead of
having one massive diagram I am creating a diagram per module.
All I'm doing is creating a new diagram, selecting all the tables
that belong to a module, and letting the software create the
diagram. I do make some format/layout changes to make the
diagram easier to read, but at no time am I making any structural
changes to the table.
For three of the four modules this approach has worked perfectly.
However, there is one set of tables that the tool thinks has been
altered, and it insists on writing the tables back to the database
before it will save it. The first time this happened I just said "No"
to any writing/saving and started over from scratch (I assumed I
had accidentally made a change to a table). The next time I added
all the module's tables, I simply moved one table two or three
inches to the left, and then tried to save the daigram (having 100%
confidence there were no accidental structural changes). Once
again, it wanted to write a few of the tables back to the database
before saving.
I have no idea why it thinks any structural changes occured to the
referenced tables. I certainly didn't make any, and on the rare
occasion I have accidentally made a change, I was able to
successfully start over by not writing/saving the change and
closing/opening the diagram.
Can anyone let me know what possible changes could have been
applied to a table(s) outside the diagram tool, that could affect the
diagram tool and make it think it needs to write the tables to the
database before saving?
ThanksHi Garth,
I don't know the answer to your question because I don't like, or use the
SQL Server diagramming tool - for the exact reason you're experiencing ...
changes to the diagram make changes to the database.
While I used to use ER/win (which is a fantastic tool), I've shifted to
Visio. Now, without the developer edition (I think that's the one) you can't
do a forward engineer, but you can reverse engineer any DB you can connect
to (ODBC, OLE DB, etc), it provides at least 80% of what matters in ER/win
(or Rational Rose) and you have the advantage that anyone with Visio can
read the file.
I admit it's going to be hard to learn it (as there is virtually no one on
the boards who know how), but I find it far, far superior to what is
available in SQL Server and more convenient than anything else.
Thanks,
Jay
"Garth Wells" <nobody@.nowhere.com> wrote in message
news:eQq7Mx1FIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Using SQL Server 2000...
> I'm creating a series of database diagrams for a database that has
> ~ 200 tables. The tables are segmented by module, so instead of
> having one massive diagram I am creating a diagram per module.
> All I'm doing is creating a new diagram, selecting all the tables
> that belong to a module, and letting the software create the
> diagram. I do make some format/layout changes to make the
> diagram easier to read, but at no time am I making any structural
> changes to the table.
> For three of the four modules this approach has worked perfectly.
> However, there is one set of tables that the tool thinks has been
> altered, and it insists on writing the tables back to the database
> before it will save it. The first time this happened I just said "No"
> to any writing/saving and started over from scratch (I assumed I
> had accidentally made a change to a table). The next time I added
> all the module's tables, I simply moved one table two or three
> inches to the left, and then tried to save the daigram (having 100%
> confidence there were no accidental structural changes). Once
> again, it wanted to write a few of the tables back to the database
> before saving.
> I have no idea why it thinks any structural changes occured to the
> referenced tables. I certainly didn't make any, and on the rare
> occasion I have accidentally made a change, I was able to
> successfully start over by not writing/saving the change and
> closing/opening the diagram.
> Can anyone let me know what possible changes could have been
> applied to a table(s) outside the diagram tool, that could affect the
> diagram tool and make it think it needs to write the tables to the
> database before saving?
> Thanks
>
>

Development/Production Environment with Visual Source Safe

Am new to RS. Installed it on test server and was quickly able to
generate a report with multiple datasources and even write some code to
render it directly to a PDF file. Quite a useful and efficient tool.
Now, we want to bring RS into our development environment. We have
multiple developers working on an internal web app in VS.NET that we
want to incorporate reports into. Developers use Visual Source Safe to
bring project files from the development server to their own machines
to do development and then check changes back into the development
server. Periodically, our app is release from development to
production. Pretty straightforward.
What I'm curious about is:
(1) Does SourceSafe version control the report definitions? They look
like files in VS .NET but they reside in the RS database, so I'm
uncertain.
(2) Can developers install RS on their machines for developing reports
under VS.NET while using the RS server/database on the development
server for previewing?
Thanks.
JeffAnswers to your questions:
1. You can (and should) check reports, report projects, report
solutions--however you want to organize it--into VSS. But it is a separate
process that you have to enforce with policy and procedure as VSS will not
reach into the report catalog (database) and handle versioning there.
2. Yes. If your developers have VS.NET 2003, then just install any version
of Reporting Services on their workstations, just unselect and server
components if they are offered in the setup.
--
Douglas McDowell douglas@.nospam.solidqualitylearning.com
"JeffW" <jwilson@.telnetww.com> wrote in message
news:1110499289.694022.73370@.g14g2000cwa.googlegroups.com...
> Am new to RS. Installed it on test server and was quickly able to
> generate a report with multiple datasources and even write some code to
> render it directly to a PDF file. Quite a useful and efficient tool.
> Now, we want to bring RS into our development environment. We have
> multiple developers working on an internal web app in VS.NET that we
> want to incorporate reports into. Developers use Visual Source Safe to
> bring project files from the development server to their own machines
> to do development and then check changes back into the development
> server. Periodically, our app is release from development to
> production. Pretty straightforward.
> What I'm curious about is:
> (1) Does SourceSafe version control the report definitions? They look
> like files in VS .NET but they reside in the RS database, so I'm
> uncertain.
> (2) Can developers install RS on their machines for developing reports
> under VS.NET while using the RS server/database on the development
> server for previewing?
> Thanks.
> Jeff
>

determining the where statement

Hello,

Does anyone know how I can write the where statement according to the value?
In other words,
a command name would determine the where statement but the select statement is always the same.

This does not work:

create procedure new_procedure
(@.cid int, @.command VarChar(25))
Select * from a table
If @.command = 'pick1' begin
Where this = @.cid and that = 'Yes'
End
Else If @.command = 'pick2' begin
Where this = @.cid and that = 'No'
End
Else If @.command = 'pick3' begin
Where this = @.cid and that = 'No' and datefield >= DateAdd(d, -5, getdate())
End

something like that there.
Any ideas?
Thanks
Ehow many distinct values for @.command do you see ? is that something fixed like 3-4 options or would you have plenty of them..if you have only 3-4 options like you have above then you can do something like:

create procedure new_procedure
(@.cid int, @.command VarChar(25)) AS
begin
If @.command = 'pick1'
 select * from table Where this = @.cid and that = 'Yes'
Else If @.command = 'pick2'
 select * from table Where this = @.cid and that = 'No'
Else If @.command = 'pick3'
 select * from table Where this = @.cid and that = 'No' and datefield >= DateAdd(d, -5,
 getdate())
end

HTH