Re: Help with Query



--CELKO-- (jcelko212@xxxxxxxxxxxxx) writes:
> After that ABSOLUTELY BASIC PIECE OF NETIQUETTE, did you read what you
> posted? What the @!$% specs for this?? Wait, wait, let me read your
> mind and guess that you want to see only those rows whose col_1 groups
> have one and only one value for col_2 !!
>...
> If you plan to stay in this trade, please learn minimal Netiquette and
> how to write a minimal specification.

No, this is not what minimal nettiquette is about. Although, including
CREATE TABLE is nice, it's mainly a good idea, because it helps to
get a good answer.

But minimal and basic nettiquette is about something else: that is about
being polite and friendly. Something you are miserable poor in.



--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

.



Relevant Pages

  • Re: Desired capacity
    ... How big a vehicle do I need to haul my family around? ... That is a difficult question to answer without knowing specifics. ... What are the specs of your current machine? ... > I am new to SQL Server, ...
    (microsoft.public.sqlserver.setup)
  • Re: excluding fields in SELECT statement
    ... I guess this is what Dan had in mind. ... There is a new product PromptSQL which claims to provide intellisense to ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)
  • Re: Access migration to SQL Server
    ... How can we convert MS-Access import specs to SQL Server. ... Regarding reports, must we leave them in Access? ... > Your main issue will be with the queries as the syntax can be slightly ...
    (microsoft.public.access.conversion)
  • Re: Access migration to SQL Server
    ... How can we convert MS-Access import specs to SQL Server. ... Regarding reports, must we leave them in Access? ... >> Your main issue will be with the queries as the syntax can be slightly ...
    (microsoft.public.access.conversion)
  • Re: Access migration to SQL Server
    ... How can we convert MS-Access import specs to SQL Server. ... Regarding reports, must we leave them in Access? ... > Your main issue will be with the queries as the syntax can be slightly ...
    (microsoft.public.sqlserver.server)