Problem on cross-tab

I want to insert Espacial field (Record number) in cross-tab report.
How is it possible?
It works nice on standered report but in cross-tab i can't do that.
eliasHello
Mr. Ello
u should write it details
so that i can----

write abt ur code|||hi siraj,

U know in standered report if u select the espacial field(Record Number)
and place it in details section then u can find the record number in the
report.

I want to do same thing in cross-tab report.

However I can't still solve ur question(2 see the total in individual page)

I did the solution which helped u to do that.(But if i place formula-3 in
report footer I can't see anything in individual page but only in last page)

If I place it in page footer then the same problem u written arises..

so help me......

ur ello|||Dear Ello
to solve my problem u can follw last help of Madhi

For ur problem i think u can use standard report & in standard report u can insert cross-tab where record count cn b used as u wish

i hv tested it :if u cn for ur problem u should inform me

bye

siraj

Problem inserting decimal data

Hi all,
I have a number of columns in an SQL server table that are of type Decimal.
The problem is, when I create a stored procedure and add decimal data to the
table, the decimal places are chopped off. The number of decimal places to
be stored is set to auto, so that should be ok.
Does anyone know what would cause this?
Thanks to anyone who can help
SimonSimon
Can you show us your INSERT statement?
CREATE TABLE #Test
(
col DECIMAL (18,2)
)
GO
INSERT INTO #Test VALUES (12.5)
INSERT INTO #Test VALUES (10.55)
INSERT INTO #Test VALUES (8.99)
GO
SELECT * FROM #Test
"Simon Harvey" <sh856531@.microsofts_free_email_service.com> wrote in message
news:ueWav8PMEHA.808@.tk2msftngp13.phx.gbl...
> Hi all,
> I have a number of columns in an SQL server table that are of type
Decimal.
> The problem is, when I create a stored procedure and add decimal data to
the
> table, the decimal places are chopped off. The number of decimal places to
> be stored is set to auto, so that should be ok.
> Does anyone know what would cause this?
> Thanks to anyone who can help
> Simon
>

Problem inserting decimal data

Hi all,
I have a number of columns in an SQL server table that are of type Decimal.
The problem is, when I create a stored procedure and add decimal data to the
table, the decimal places are chopped off. The number of decimal places to
be stored is set to auto, so that should be ok.
Does anyone know what would cause this?
Thanks to anyone who can help
Simon
Simon
Can you show us your INSERT statement?
CREATE TABLE #Test
(
col DECIMAL (18,2)
)
GO
INSERT INTO #Test VALUES (12.5)
INSERT INTO #Test VALUES (10.55)
INSERT INTO #Test VALUES (8.99)
GO
SELECT * FROM #Test
"Simon Harvey" <sh856531@.microsofts_free_email_service.com> wrote in message
news:ueWav8PMEHA.808@.tk2msftngp13.phx.gbl...
> Hi all,
> I have a number of columns in an SQL server table that are of type
Decimal.
> The problem is, when I create a stored procedure and add decimal data to
the
> table, the decimal places are chopped off. The number of decimal places to
> be stored is set to auto, so that should be ok.
> Does anyone know what would cause this?
> Thanks to anyone who can help
> Simon
>

Problem inserting decimal data

Hi all,
I have a number of columns in an SQL server table that are of type Decimal.
The problem is, when I create a stored procedure and add decimal data to the
table, the decimal places are chopped off. The number of decimal places to
be stored is set to auto, so that should be ok.
Does anyone know what would cause this?
Thanks to anyone who can help
SimonSimon
Can you show us your INSERT statement?
CREATE TABLE #Test
(
col DECIMAL (18,2)
)
GO
INSERT INTO #Test VALUES (12.5)
INSERT INTO #Test VALUES (10.55)
INSERT INTO #Test VALUES (8.99)
GO
SELECT * FROM #Test
"Simon Harvey" <sh856531@.microsofts_free_email_service.com> wrote in message
news:ueWav8PMEHA.808@.tk2msftngp13.phx.gbl...
> Hi all,
> I have a number of columns in an SQL server table that are of type
Decimal.
> The problem is, when I create a stored procedure and add decimal data to
the
> table, the decimal places are chopped off. The number of decimal places to
> be stored is set to auto, so that should be ok.
> Does anyone know what would cause this?
> Thanks to anyone who can help
> Simon
>