Friday, March 23, 2012
point labels bar charts
using pie charts. Can someone verify this for me or let me know what I am
doing wrong? Chart type is column, delselected Auto and chose right but the
label is still in the middle of the column area.
Also, we would like to be able to control overlaping labels. I saw a
posting that this is not supported - is this true and will it be supported in
the next version?
Thanks!If you check "Auto" for the datapoint label position, then the labels should
never overlap (unless you have a stacked column/bar chart where it can still
happen).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"debra doty" <debradoty@.discussions.microsoft.com> wrote in message
news:395CDF6E-AC41-48BE-83C2-1112FABFC60F@.microsoft.com...
> It looks to me like you can only place point labels outside of the chart
when
> using pie charts. Can someone verify this for me or let me know what I am
> doing wrong? Chart type is column, delselected Auto and chose right but
the
> label is still in the middle of the column area.
> Also, we would like to be able to control overlaping labels. I saw a
> posting that this is not supported - is this true and will it be supported
in
> the next version?
> Thanks!|||But they do overlap. Mainly we are having a problem with lines on bar
charts. Point labels on the lines are overlapping point labels on the bars
as well as other lines. Auto is selected.
"Robert Bruckner [MSFT]" wrote:
> If you check "Auto" for the datapoint label position, then the labels should
> never overlap (unless you have a stacked column/bar chart where it can still
> happen).
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "debra doty" <debradoty@.discussions.microsoft.com> wrote in message
> news:395CDF6E-AC41-48BE-83C2-1112FABFC60F@.microsoft.com...
> > It looks to me like you can only place point labels outside of the chart
> when
> > using pie charts. Can someone verify this for me or let me know what I am
> > doing wrong? Chart type is column, delselected Auto and chose right but
> the
> > label is still in the middle of the column area.
> >
> > Also, we would like to be able to control overlaping labels. I saw a
> > posting that this is not supported - is this true and will it be supported
> in
> > the next version?
> >
> > Thanks!
>
>|||I just double checked the behavior to be sure I was stating it clearly. When
auto is selected, the line point labels overlap the bar point labels. When
auto is not selected, we don't get the arrow pointing to the line the label
is for. This is a problem for lines that are close to each other. Because
the labels can't appear outside of the chart, part of the text is chopped
off.
If we could set the line point labels to display outside of the graph, we
wouldn't have this problem. I guess I am asking to put this on the wish list.
"debra doty" wrote:
> But they do overlap. Mainly we are having a problem with lines on bar
> charts. Point labels on the lines are overlapping point labels on the bars
> as well as other lines. Auto is selected.
> "Robert Bruckner [MSFT]" wrote:
> > If you check "Auto" for the datapoint label position, then the labels should
> > never overlap (unless you have a stacked column/bar chart where it can still
> > happen).
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > "debra doty" <debradoty@.discussions.microsoft.com> wrote in message
> > news:395CDF6E-AC41-48BE-83C2-1112FABFC60F@.microsoft.com...
> > > It looks to me like you can only place point labels outside of the chart
> > when
> > > using pie charts. Can someone verify this for me or let me know what I am
> > > doing wrong? Chart type is column, delselected Auto and chose right but
> > the
> > > label is still in the middle of the column area.
> > >
> > > Also, we would like to be able to control overlaping labels. I saw a
> > > posting that this is not supported - is this true and will it be supported
> > in
> > > the next version?
> > >
> > > Thanks!
> >
> >
> >|||If we set all of the point labels (for all lines and all bars) to Auto, they
do not overlap. But, the numbers are all strewn over the report so no human
being could possibly read it.
We should be able to tell some data values to move their point labels
automatically and set other values. Having the line point lables outside of
the chart would also solve our problem.
"debra doty" wrote:
> But they do overlap. Mainly we are having a problem with lines on bar
> charts. Point labels on the lines are overlapping point labels on the bars
> as well as other lines. Auto is selected.
> "Robert Bruckner [MSFT]" wrote:
> > If you check "Auto" for the datapoint label position, then the labels should
> > never overlap (unless you have a stacked column/bar chart where it can still
> > happen).
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > "debra doty" <debradoty@.discussions.microsoft.com> wrote in message
> > news:395CDF6E-AC41-48BE-83C2-1112FABFC60F@.microsoft.com...
> > > It looks to me like you can only place point labels outside of the chart
> > when
> > > using pie charts. Can someone verify this for me or let me know what I am
> > > doing wrong? Chart type is column, delselected Auto and chose right but
> > the
> > > label is still in the middle of the column area.
> > >
> > > Also, we would like to be able to control overlaping labels. I saw a
> > > posting that this is not supported - is this true and will it be supported
> > in
> > > the next version?
> > >
> > > Thanks!
> >
> >
> >
Friday, March 9, 2012
Please verify this SQL fragment
Will someone please help verify this SQL fragment?
I want to ensure that it produces the same results as the 'Group By' clause of the MS Access fragment below.
T-SQL:
Group By Case
When r.LICFAC In ('CR', 'GC') And f.SOPNO < 38 Then -1
Else 0
End
, Case
When r.LICFAC = 'MU' And f.SOSTS <> '05' Then -1
Else 0
End
MS Access:GROUP BY IIf((([LICFAC]="CR" Or [LICFAC]="GC") And ([SOPNO]<38)),True,False)
, IIf(([LICFAC]="MU") And ([SOSTS]<>"05"),True,False)
Seems to be ok. Did you test it?
AMB
|||Thanks, Hunchback.
The query is failing. I get a message saying that the SOPNO and SOSTS fields are invalid because they are not contained in either an aggregate function or the GROUP BY clause.
Msg 8121, Level 16, State 1, Line 58
Column 'CSAS400.RCHASE5C.BPCSFFG.FSOL02.SOPNO' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause.
Msg 8121, Level 16, State 1, Line 58
Column 'CSAS400.RCHASE5C.BPCSFFG.FSOL02.SOSTS' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause.
That true, of course.
The query works in MS Access.
Is there a way to restructure the query so that I get the same results as the Access query?
Here is the entire query:
Thanks,
Insert Into Rep2
Select LICFAC
, HORD
, HSAL
, CHBCON
, CHCRDH
, CHUSRH
, SUM(Amt) As SumOfAmount
, Min(SchedDate) As MinOfSchedDate
, Min(OrigDate) As MinOfOrigDate
, CNME
, SNAME
From #Rep1 r
Inner Join CSAS400.RCHASE5C.BPCSFFG.FSOL02 f On r.CLSORD = f.SCORD
And r.HORD = f.SCORD
Group By r.LICFAC
, r.HORD
, r.HSAL
, r.CHBCON
, r.CHCRDH
, r.CHUSRH
, r.CNME
, r.SNAME
, f.SID
, Case
When r.LICFAC In ('CR', 'GC') And f.SOPNO < 38 Then -1
Else 0
End
, Case
When r.LICFAC = 'MU' And f.SOSTS <> '05' Then -1
Else 0
End
Having f.SID = 'SO'
|||And Not (
r.LICFAC In ('CR', 'GC')
And
f.SOPNO < 38
)
And Not (
r.LICFAC = 'MU'
And
f.SOSTS <> '05'
);
Why in the having clause? It is mostly used to filter the result of the "group by" clause or an aggregate function. Can you test putting that expression in the "where" clause".
AMB
|||Thanks again, Hunchback! I placed the filter in the "where" clause.please verify syntax
I haven't written any .net database updates before. I wrote the following code for a visual web developer application and it appears to work. There is no close function or anything. Will the adapter, builder, dataset, and row objects be cleaned up and disposed of properly? Please tell me if I need to include anything else. The connection object is made elsewhere. Thanks
Dim adapterAsNew Data.SqlClient.SqlDataAdapter("SELECT * FROM Inventory WHERE InUnique=" & ListValue.Value, connect)Dim builderAsNew Data.SqlClient.SqlCommandBuilder(adapter)
Dim datasetAs Data.DataSet =New Data.DataSet()adapter.Fill(dataset,"Inventory")
Dim datarowAs Data.DataRow = dataset.Tables(0).Rows(0)datarow("InAgUnique") = Val(InAgUnique.Text)
datarow("InTyUnique") = Val(InTyUnique.Text)datarow("InName") = InName.Text
datarow("InPnUniquePrimary") = Val(InPnUniquePrimary.Text)datarow("InPnUniqueSecondary") = Val(InPnUniqueSecondary.Text)
datarow("InPnUniqueTertiary") = Val(InPnUniqueTertiary.Text)datarow("InPnUniqueSupervisor") = Val(InPnUniqueSupervisor.Text)
datarow("InDescription") = InDescription.Textdatarow("InProblemInstructions") = InProblemInstructions.Text
adapter.Update(dataset,"Inventory")
If the connection is not open, Adapter would open it and once done with the operation, would close itself (as per .net 1.1), not sure of the chanegs in 2.0 though!
Please verify SQL Server is running and check your SQL
The EU is trying to connect to the SQL Server database
through EM at her desk and she gets the following error
message.
"A connection could not be established to [SERVER NAME] -
specified driver could not be loaded due to system error
126 (SQL Server).
Please verify SQL Server is running and check your SQL
Servcer registration properties (by right-clicking on the
SERVER node) and try again."
These were the steps that were taken to ensure that the
above error could be resolved but invain......
1. Uninstalled SQL SERVER Enterprise Manager on Customers
PC and
reinstalled it - This did not help. Still getting the
following error
message.
(See attached file: sql server error.jpg)
2. Based on some of the information I tried searching for
sqlsrv32.dll file
location and were it was referencing in the registry and
found that it was
referencing to a drive mapping called S:\HR750
\crwxxx\sqlsrv32.dll - This
drive was formerly a people soft mapping which the
customer was using so, I
changed the registry settings to point to the dll file
which resided in
C:\WINNT\SYSTEM32 location, but that also did not help.
3. Made sure that all her patches and MDAC were proper and
fully patched.
Updated it but neither did this help.
4. Checked to see see whether Login Timeout could be
changed from default
of 4 to 8, but was unsuccessful int getting into that
options on the EM.
5. It looks more that some dll is corrupt which is causing
this problem on
the customres PC. I tried accessing ODBC Settings and
selected SQL Server
Driver and I get the following error message
"The setup routines for the SQL Server ODBC driver should
not be loaded due
to system error code 126"
and when I click on "OK", I get the next screen which has
a title
Driver's ConfigDSN, ConfigDriver, or Config Translator
failed
"Could not load the setup or translator library"
It sounds like a corrupt MDAC installation. Reinstalling the current
version of MDAC is a tricky proposition. If you have not upgraded to MDAC
2.8 on this machine you could do that and more than likely resolve this
problem.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Monday, February 20, 2012
Please Help! Service Pack update Cannot Verify User with SA login
Services & Manager,Decision Service Objects and Client Components. Afterwards
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?
Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwards
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says it
> could not verify user even though I have even changed the password and know
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?
Please Help! Service Pack update Cannot Verify User with SA login
Services & Manager,Decision Service Objects and Client Components. Afterward
s
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwa
rds
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says i
t
> could not verify user even though I have even changed the password and kno
w
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?
Please Help! Service Pack update Cannot Verify User with SA login
Services & Manager,Decision Service Objects and Client Components. Afterwards
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwards
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says it
> could not verify user even though I have even changed the password and know
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?