FOR XML in web page- OK what's next

(1) I need to select records from a SQL database and create a XML document which I then need to write to a users directory. I am using SQL express with VWD 2005. I located the FOR XML and can execute in VWD's SQL graphical tool. I haven't tried in a Web Form yet but I assume it will work ok. But then how do I write the xml results from the SQL query to local user's directory?

(2) I can execute the FOR XML in the SQL graphical tool but how do i Connect to the DB in the Web Form? Use data.sqlClient.Connection and use .SQLcommand to perform the SQL query? If so, then what?

Following is an example I found that shows use of a NameSpace

WITH XMLNAMESPACES (DEFAULT 'urn:example.com/doc'

, 'urn:example.com/customer' as "c"

, 'urn:example.com/order' as"o"

)

SELECT CustomerID as "@.ID",

(SELECT OrderID as "@.OrderID"

from Orders

where Customers.CustomerID=Orders.CustomerID

FOR XML PATH('o:Order'), TYPE

) as "c:Orders",

CompanyName as "c:CompanyName",

ContactTitle as "c:ContactName/@.ContactTitle",

ContactName as "c:ContactName/text()",

PostalCode as "c:Address/@.ZIP",

Address as "c:Address/c:Street",

City as "c:Address/c:City"

FROM Customers

FOR XML PATH('c:Customer'), ROOT('doc')

My research turns up nothing on the above. Is FOR SQL the best way to go? I see that the SQLXML is not available in SQL server express 2005.

Thanks for any help.

Pauley

Once you have the data in a dataset you can write the XML to a file(froma datatable as well if you want) Link is here;

http://msdn2.microsoft.com/en-us/library/zx8h06sz.aspx

To do this you do not need to use for xml or even the XML-DT on the server.

FOR XML EXPLICIT - Insert XML Data into a different Table

Greetings,
How do I insert the XML document returned from the usage of FOR XML Explicit
into a different table within a Stored Procedure.
I have been able to use the FOR XML Explicit to generate the XML document
but I need to insert it into a different table as a Text value.
TIA,
KOYIf you are using SQL Server 2005, you can just insert it. In SQL Server
2000, FOR XML results have to be returned to the client-side. So you would
have to write an OLEDB/ADO program that returns the data and then reinserts
it. If you need to drive it from the server, you can use the sp_OA stored
procs.
But the best thing would be to get the April CTP of SQL Server 2005 if
running Beta software is an option...
Best regards
Michael
"Kayode Yusuf" <KayodeYusuf@.discussions.microsoft.com> wrote in message
news:8693AAA4-B0BE-4926-A179-2039BC811F1C@.microsoft.com...
> Greetings,
> How do I insert the XML document returned from the usage of FOR XML
> Explicit
> into a different table within a Stored Procedure.
> I have been able to use the FOR XML Explicit to generate the XML document
> but I need to insert it into a different table as a Text value.
> TIA,
> KOY

FOR XML EXPLICIT - Insert XML Data into a different Table

Greetings,
How do I insert the XML document returned from the usage of FOR XML Explicit
into a different table within a Stored Procedure.
I have been able to use the FOR XML Explicit to generate the XML document
but I need to insert it into a different table as a Text value.
TIA,
KOY
If you are using SQL Server 2005, you can just insert it. In SQL Server
2000, FOR XML results have to be returned to the client-side. So you would
have to write an OLEDB/ADO program that returns the data and then reinserts
it. If you need to drive it from the server, you can use the sp_OA stored
procs.
But the best thing would be to get the April CTP of SQL Server 2005 if
running Beta software is an option...
Best regards
Michael
"Kayode Yusuf" <KayodeYusuf@.discussions.microsoft.com> wrote in message
news:8693AAA4-B0BE-4926-A179-2039BC811F1C@.microsoft.com...
> Greetings,
> How do I insert the XML document returned from the usage of FOR XML
> Explicit
> into a different table within a Stored Procedure.
> I have been able to use the FOR XML Explicit to generate the XML document
> but I need to insert it into a different table as a Text value.
> TIA,
> KOY

FOR XML Explicit

Greetings,
How do I insert the XML document returned from the usage of FOR XML Explicit
into a different table within a Stored Procedure.
I have been able to use the FOR XML Explicit to generate the XML document
but I need to insert it into a different table as a Text value.
TIA,
KOYI don't think you can do this directly with T-SQL in SQL Server 2000. You
will probably need an application to do this.
I thought perhaps you could create a temp table with a single ntext field
and then do INSERT #temp SELECT ... FOR XML EXPLICIT, but the INSERT
statement doesn't allow you to use the FOR XML clause.
If your system can handle the transfer to the TEXT field being done in
batch-mode, rather than immediately, you could have an app that was launched
by SQL Agent that read the XML in and then inserted the text into a text
field; cheesy but do-able.
Mike|||Unfortunately, you will have to extract the data out and then import back
in. Some archive to get you started.
http://groups.google.co.uk/groups?q...ver+oj+textcopy
-oj
"Kayode Yusuf" <KayodeYusuf@.discussions.microsoft.com> wrote in message
news:14FF705A-EC18-4FC0-ABFE-18041AC132B4@.microsoft.com...
> Greetings,
> How do I insert the XML document returned from the usage of FOR XML
> Explicit
> into a different table within a Stored Procedure.
> I have been able to use the FOR XML Explicit to generate the XML document
> but I need to insert it into a different table as a Text value.
> TIA,
> KOY

FOR XML AUTO not producing the proper parent-child hierarchy

I have a query that uses two views that should produce a simple parent-child
XML document however it repeats every
parent (topic) record for each child record. Here's the query:
select topic.id,
topic.name,
topic.sename,
topic.description,
topic.parentsubjectname,
topic.parentcategroyname,
0 WL,
item.id,
item.name,
item.sename,
item.about,
item.avgrating
from dbo.pico_topic_info topic
join dbo.pico_item_info item on topic.id = item.ParentTopicID
where topic.id = 344
order by topic.id, item.id
for xml auto, elements
I expect a document that looks like this:
<topic>
<id>344</id>
<name>Some Topic</name>
..
<item>
<id>123123</id>
<name>item 1 </name>
..
</item>
<item>
<id>543453</id>
<name>item 2</name>
..
</item>
</topic>
However I get a topic element with every item element:
<topic>
<id>344</id>
<name>Some Topic</name>
..
<item>
<id>123123</id>
<name>item 1 </name>
..
</item>
</topic>
<topic>
<id>344</id>
<name>Some Topic</name>
..
<item>
<id>543453</id>
<name>item 2</name>
..
</item>
</topic>
Any ideas why? I've not had this problem before.
--BuddyWell, I figured it out. The description column is an ntext column which app
arently doesn't play well with other columns
when the FOR XML clause is used.
--Buddy
Buddy Ackerman wrote:
> I have a query that uses two views that should produce a simple
> parent-child XML document however it repeats every parent (topic) record
> for each child record. Here's the query:
>
> select topic.id,
> topic.name,
> topic.sename,
> topic.description,
> topic.parentsubjectname,
> topic.parentcategroyname,
> 0 WL,
> item.id,
> item.name,
> item.sename,
> item.about,
> item.avgrating
> from dbo.pico_topic_info topic
> join dbo.pico_item_info item on topic.id = item.ParentTopicID
> where topic.id = 344
> order by topic.id, item.id
> for xml auto, elements
>
> I expect a document that looks like this:
> <topic>
> <id>344</id>
> <name>Some Topic</name>
> ...
> <item>
> <id>123123</id>
> <name>item 1 </name>
> ...
> </item>
> <item>
> <id>543453</id>
> <name>item 2</name>
> ...
> </item>
> </topic>
> However I get a topic element with every item element:
>
>
> <topic>
> <id>344</id>
> <name>Some Topic</name>
> ...
> <item>
> <id>123123</id>
> <name>item 1 </name>
> ...
> </item>
> </topic>
> <topic>
> <id>344</id>
> <name>Some Topic</name>
> ...
> <item>
> <id>543453</id>
> <name>item 2</name>
> ...
> </item>
> </topic>
>
> Any ideas why? I've not had this problem before.
>
> --Buddy

FOR XML AUTO not producing the proper parent-child hierarchy

I have a query that uses two views that should produce a simple parent-child XML document however it repeats every
parent (topic) record for each child record. Here's the query:
select topic.id,
topic.name,
topic.sename,
topic.description,
topic.parentsubjectname,
topic.parentcategroyname,
0 WL,
item.id,
item.name,
item.sename,
item.about,
item.avgrating
from dbo.pico_topic_info topic
join dbo.pico_item_info item on topic.id = item.ParentTopicID
where topic.id = 344
order by topic.id, item.id
for xml auto, elements
I expect a document that looks like this:
<topic>
<id>344</id>
<name>Some Topic</name>
...
<item>
<id>123123</id>
<name>item 1 </name>
...
</item>
<item>
<id>543453</id>
<name>item 2</name>
...
</item>
</topic>
However I get a topic element with every item element:
<topic>
<id>344</id>
<name>Some Topic</name>
...
<item>
<id>123123</id>
<name>item 1 </name>
...
</item>
</topic>
<topic>
<id>344</id>
<name>Some Topic</name>
...
<item>
<id>543453</id>
<name>item 2</name>
...
</item>
</topic>
Any ideas why? I've not had this problem before.
--Buddy
Well, I figured it out. The description column is an ntext column which apparently doesn't play well with other columns
when the FOR XML clause is used.
--Buddy
Buddy Ackerman wrote:
> I have a query that uses two views that should produce a simple
> parent-child XML document however it repeats every parent (topic) record
> for each child record. Here's the query:
>
> select topic.id,
> topic.name,
> topic.sename,
> topic.description,
> topic.parentsubjectname,
> topic.parentcategroyname,
> 0 WL,
> item.id,
> item.name,
> item.sename,
> item.about,
> item.avgrating
> from dbo.pico_topic_info topic
> join dbo.pico_item_info item on topic.id = item.ParentTopicID
> where topic.id = 344
> order by topic.id, item.id
> for xml auto, elements
>
> I expect a document that looks like this:
> <topic>
> <id>344</id>
> <name>Some Topic</name>
> ...
> <item>
> <id>123123</id>
> <name>item 1 </name>
> ...
> </item>
> <item>
> <id>543453</id>
> <name>item 2</name>
> ...
> </item>
> </topic>
> However I get a topic element with every item element:
>
>
> <topic>
> <id>344</id>
> <name>Some Topic</name>
> ...
> <item>
> <id>123123</id>
> <name>item 1 </name>
> ...
> </item>
> </topic>
> <topic>
> <id>344</id>
> <name>Some Topic</name>
> ...
> <item>
> <id>543453</id>
> <name>item 2</name>
> ...
> </item>
> </topic>
>
> Any ideas why? I've not had this problem before.
>
> --Buddy

FOR XML / stored procedures

Does anyone know how to generate a resultset using FOR XML
and save that result (XML document) into a column without
leaving SQL Server to render the document?I dont think this is possible as the FOR XML clause sends a stream data out
and it is not possible to save it into a varible at the SQL Server in the
current version atleast ...
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD
www.extremeexperts.com
"T. Wade" <tnolte@.foundrysoftware.com> wrote in message
news:04ac01c366a0$fe916d90$a401280a@.phx.gbl...
> Does anyone know how to generate a resultset using FOR XML
> and save that result (XML document) into a column without
> leaving SQL Server to render the document?|||Hello Wade,
Thanks for posting to MSDN Managed Newsgroup. I will look into this issue
and
let you know as soon as I have update for you.
Thanks,
Vikrant Dalwale
Microsoft SQL Server Support Professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure !! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.
--
>Content-Class: urn:content-classes:message
>From: "T. Wade" <tnolte@.foundrysoftware.com>
>Sender: "T. Wade" <tnolte@.foundrysoftware.com>
>Subject: FOR XML / stored procedures
>Date: Tue, 19 Aug 2003 15:26:54 -0700
>Lines: 3
>Message-ID: <04ac01c366a0$fe916d90$a401280a@.phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Thread-Index: AcNmoP6RD2nsbfwKTKGJ1OA7aiz6og==>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Newsgroups: microsoft.public.sqlserver.server
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:302172
>NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Does anyone know how to generate a resultset using FOR XML
>and save that result (XML document) into a column without
>leaving SQL Server to render the document?
>|||Hello Wade,
There isn?t a way to do this without going out to a client and back in.
The FOR XML formatting of the recordset is done as the last step when the
TDS output stream is created so the output has to leave the server.
One workaround could be to use link servers by linking a server back to
itself. Ken Henderson's book contains related information
http://btobsearch.barnesandnoble.com/booksearch/isbnInquiry.asp?userid=2VOBU
N18XR&btob=Y&isbn=0201700468&itm=1
[ Disclaimer: This is a third party info and Microsoft does not guarantee
the accuracy of it]
In above case, the data is still being streamed out of the server through
the OLEDB provider so you might wanna watch the performance.
Thanks for posting to MSDN Managed Newsgroup.
Vikrant Dalwale
Microsoft SQL Server Support Professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure !! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.
--
>Content-Class: urn:content-classes:message
>From: "T. Wade" <tnolte@.foundrysoftware.com>
>Sender: "T. Wade" <tnolte@.foundrysoftware.com>
>Subject: FOR XML / stored procedures
>Date: Tue, 19 Aug 2003 15:26:54 -0700
>Lines: 3
>Message-ID: <04ac01c366a0$fe916d90$a401280a@.phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Thread-Index: AcNmoP6RD2nsbfwKTKGJ1OA7aiz6og==>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Newsgroups: microsoft.public.sqlserver.server
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:302172
>NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Does anyone know how to generate a resultset using FOR XML
>and save that result (XML document) into a column without
>leaving SQL Server to render the document?
>

For security reasons DTD is prohibited in this XML document.

When we develop with the Microsoft SQL Server 2005 Reporting Service.
We got the exception on some reports.

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on
XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Ther report renders well first time, but if we click the title to sort the report, it will throw the exception.

And It occurred that we use IE6 and IE7 to view the report at same time, but if we use the same version brower, there are no exception.
Can somebody help me?

My development’s environment :
Windows XP English Professional + SP2
Microsoft SQL Server 2005 Development version + SP 1 + SP 2
Microsoft Visual Studio 2005 Professional Version 8.0.50727.51 (QFE.050727-5100) + SP1
Microsoft .NET Framework Version 2.0.50727

Hi Kevin,

We found an issue like this in a recent version of pre-release SQL 2005 Reporting Services SP2. If you are running versions of Reporting Services prior to SP2, please let me know. Otherwise, this will be fixed in the the final release of SP2.

|||

I'm seeing this occur in both SP1, and the CTP release of SP2.

Please advise. Reports render some of the time, but the vast majority I revceive the same error.

|||

We just installed SP2 in our organization. I am running a very large dataset which brings out about 4 million rows. When I run this report I am getting this error.

For security reasons DTD is prohibited in this XML document......

Please help...

For security reasons DTD is prohibited in this XML document.

When we develop with the Microsoft SQL Server 2005 Reporting Service.
We got the exception on some reports.

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on
XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Ther report renders well first time, but if we click the title to sort the report, it will throw the exception.

And It occurred that we use IE6 and IE7 to view the report at same time, but if we use the same version brower, there are no exception.
Can somebody help me?

My development’s environment :
Windows XP English Professional + SP2
Microsoft SQL Server 2005 Development version + SP 1 + SP 2
Microsoft Visual Studio 2005 Professional Version 8.0.50727.51 (QFE.050727-5100) + SP1
Microsoft .NET Framework Version 2.0.50727

Hi Kevin,

We found an issue like this in a recent version of pre-release SQL 2005 Reporting Services SP2. If you are running versions of Reporting Services prior to SP2, please let me know. Otherwise, this will be fixed in the the final release of SP2.

|||

I'm seeing this occur in both SP1, and the CTP release of SP2.

Please advise. Reports render some of the time, but the vast majority I revceive the same error.

|||

We just installed SP2 in our organization. I am running a very large dataset which brings out about 4 million rows. When I run this report I am getting this error.

For security reasons DTD is prohibited in this XML document......

Please help...

For security reasons DTD is prohibited in this XML document and System.OutOfMemory

I am getting this error while running a very large dataset. Please help..

The full description of the error is : "For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method."

I am having hard time figuring out a solution for this. I am using sql 05, SSRS 05, Report viewer

I have a very big Dataset which pulls up millions of rows.

When I pass parameters from Windows forms to run on Reportviewer through webservice it is giving me "System.OutOfMemory" Exception and when I pass same parameters on the server(i.e. http:\\server\reportmanager) it is giving me this error "For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method".

I have no problem when I pass small dataset.

Please help me solve this annoying this problem.

|||

I found this article and i guess this should answer your question.

http://support.microsoft.com/default.aspx/kb/909678

|||

Thanks Chaitanya for the informative link.

I've already checked that and done necessary changes for the long running reports.

Right now I was able to print 55541 pages. We decided to take printout in batches if the requirement more than 55541. They best possible solution would be schedule a report and call it from Windows service using webservices.

Please let me know if we can print unlimited pages(i.e about 3 million pages).

For security reasons DTD is prohibited in this XML document

I am getting this error while running a very large dataset. Please help..

The full description of the error is : "For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method."

I am having hard time figuring out a solution for this. I am using sql 05, SSRS 05, Report viewer

I have a very big Dataset which pulls up millions of rows.

When I pass parameters from Windows forms to run on Reportviewer through webservice it is giving me "System.OutOfMemory" Exception and when I pass same parameters on the server(i.e. http:\\server\reportmanager) it is giving me this error "For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method".

I have no problem when I pass small dataset.

Please help me solve this annoying this problem.

|||

I found this article and i guess this should answer your question.

http://support.microsoft.com/default.aspx/kb/909678

|||

Thanks Chaitanya for the informative link.

I've already checked that and done necessary changes for the long running reports.

Right now I was able to print 55541 pages. We decided to take printout in batches if the requirement more than 55541. They best possible solution would be schedule a report and call it from Windows service using webservices.

Please let me know if we can print unlimited pages(i.e about 3 million pages).

For security reasons DTD is prohibited in this XML document

I have seen one other post about this and using IP addressing rather that DNS names - I am using DNS.

I have a large report that runs fine in report manager, but as soon as I try and export it to Excel it takes an age to run and I get the above error.

Any ideas anyone?

Oh, and I export loads of other reports to Excel with no problems on the same server.

More info: Curiously, I can output to pdf, xml, in fact anything except Excel.

I'm stumped

|||I can confirm that I am getting the same error when exporting with the excel plugin with large amounts of data. All other plugins work fine, just excel that's causing problems.|||

We've seen a few customers who have seen this and I'm trying to get a repro. I've tried using reports that use large result sets but cannot go beyond a certain number of rows as there is a max row limit in Excel. Then I tried to use a wide data set. Sure enough, it takes a long time when exporting to Excel but ultimately it succeeds. I've tried applying some memory pressure as well. I'm not sure if there is anything about the report or other settings that may be causing this. It will be great if you can provide additional details.

Thanks,

Sharmila

|||

I have sent a reporting services error log to someone at MS - can't remember whom and I'm not at work till next week to check my email.

It seems to be a large result set and only when rendering to Excel. Calling the report directly from within an ASP page (with the parameter to render directly to Excel) makes no difference. There are not memory problems as far as I can see, because I have tried it when the server is very quiet - with the same result. It must be a setting somewhere.

|||Sharmila - I could try and send you a data source and report if you like to see if the same thing happens on your system|||

This is now happening on a large number of reports in our reporting regime. Does anyone have a clue as to whats causing this?

Server is Windopws 2003 SP1, all clients are Windows XP SP2

|||

Please see this related thread

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=291873&SiteID=1

|||

Sure, you can send it to sharmila dot vijayan at microsoft dot com.

Thanks,

Sharmila

|||

Can you send me the report and other details in order for me to get a repro?

Thanks,

Sharmila

|||RDL, Data and dataset (in the form of a spreadsheet - must be pulled into an SQL server table to work) sent to Sharmila|||

I have the same issue when I tried to export reports to excel, pdf and other formats. I can display reports on aspx page. I can even pass parameters from the ASPX page from the buttonclick event. Everything works fine except the export option. How did you guys fix your problem? Anyhelp is highly appreciated. Thanks, Sundar

For security reasons DTD is prohibited in this XML document

I have seen one other post about this and using IP addressing rather that DNS names - I am using DNS.

I have a large report that runs fine in report manager, but as soon as I try and export it to Excel it takes an age to run and I get the above error.

Any ideas anyone?

Oh, and I export loads of other reports to Excel with no problems on the same server.

More info: Curiously, I can output to pdf, xml, in fact anything except Excel.

I'm stumped

|||I can confirm that I am getting the same error when exporting with the excel plugin with large amounts of data. All other plugins work fine, just excel that's causing problems.|||

We've seen a few customers who have seen this and I'm trying to get a repro. I've tried using reports that use large result sets but cannot go beyond a certain number of rows as there is a max row limit in Excel. Then I tried to use a wide data set. Sure enough, it takes a long time when exporting to Excel but ultimately it succeeds. I've tried applying some memory pressure as well. I'm not sure if there is anything about the report or other settings that may be causing this. It will be great if you can provide additional details.

Thanks,

Sharmila

|||

I have sent a reporting services error log to someone at MS - can't remember whom and I'm not at work till next week to check my email.

It seems to be a large result set and only when rendering to Excel. Calling the report directly from within an ASP page (with the parameter to render directly to Excel) makes no difference. There are not memory problems as far as I can see, because I have tried it when the server is very quiet - with the same result. It must be a setting somewhere.

|||Sharmila - I could try and send you a data source and report if you like to see if the same thing happens on your system|||

This is now happening on a large number of reports in our reporting regime. Does anyone have a clue as to whats causing this?

Server is Windopws 2003 SP1, all clients are Windows XP SP2

|||

Please see this related thread

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=291873&SiteID=1

|||

Sure, you can send it to sharmila dot vijayan at microsoft dot com.

Thanks,

Sharmila

|||

Can you send me the report and other details in order for me to get a repro?

Thanks,

Sharmila

|||RDL, Data and dataset (in the form of a spreadsheet - must be pulled into an SQL server table to work) sent to Sharmila|||

I have the same issue when I tried to export reports to excel, pdf and other formats. I can display reports on aspx page. I can even pass parameters from the ASPX page from the buttonclick event. Everything works fine except the export option. How did you guys fix your problem? Anyhelp is highly appreciated. Thanks, Sundar