|
Helo 
I know that I have done this before, controling howe the output-xml is formated.
The default i:
<newdataset>
<col1>val<col2>val
<col1>val<col2>val
But I want it to be:
<newdataset>
What is the property to set ????
|
|
|
|
|
And the xml visible.....
The default i:
<NewDataSet>
<table>
<col1>val</col1>
<col2>val</col2>
</table>
<table>
<col1>val</col1>
<col2>val</col2>
</table>
<NewDataSet>
But I want it to be:
<NewDataSet>
<table col1="val" col2="val">
<table col1="val" col2="val">
</NewDataSet>
What is the property to set ????
|
|
|
|
|
I answered your question in the C# forum.
|
|
|
|
|
Hi weird bug
on some PC's using a cdaodatabase to open(or create) a .mdb file,
the app crashes (yes i am trying to catch the cdaoexception), not on all PC's but they all do have office with access so you would think it would be ok
weird coz i cant seem to predict which PC's the code will crash on!
has anyone encountered this before?
Bryce
---
Publitor, making Pubmed easy.
http://www.sohocode.com/publitor
|
|
|
|
|
Try establishing a pattern for the crash.
Try checking the MDAC versions on the machines where it crashes and compare that to the MDAC versions on the machines where it doesn't.
|
|
|
|
|
indeed 
one of them has office xp installed, so one would assume that a suitable version of mdac would have been installed
Bryce
---
Publitor, making Pubmed easy.
http://www.sohocode.com/publitor
|
|
|
|
|
is there a way to hook on system stored procedures or replace it, i want to hook or replace sp_who2, is there a way?, im using sql server 2000
|
|
|
|
|
This is NOT recommended since other users might rely on the system stored procedure for correct functionality.
However, you can replace them by going into the master database, dropping the procedure and then recreating it.
|
|
|
|
|
thanks let me try it
"Now I guess I'll sit back and watch people misinterpret what I just said......"
Christian Graus At The Soapbox
[^]
|
|
|
|
|
but i cant drop it i get an error 
"Now I guess I'll sit back and watch people misinterpret what I just said......"
Christian Graus At The Soapbox
[^]
|
|
|
|
|
|
ok sorry.. forgot to tell you.. you need to perform the following steps first to enable changing of system stored procedures:
<br />
execute sp_configure 'allow updates',1<br />
go<br />
reconfigure with override<br />
go<br />
Once you are done, set allow updates to 0:
<br />
execute sp_configure 'allow updates',0<br />
go<br />
reconfigure with override<br />
go<br />
You do know that this is highly unsupported and not recommended..
|
|
|
|
|
still doesn`t work i dont know why, any other idea?, thanx for the help  .
"Now I guess I'll sit back and watch people misinterpret what I just said......"
Christian Graus At The Soapbox
[^]
|
|
|
|
|
Please tell me what error you are getting.
|
|
|
|
|
i get a messagebox telling me that i cant erease system objects, im trying to delete sp_who from master database.
"Now I guess I'll sit back and watch people misinterpret what I just said......"
Christian Graus At The Soapbox
[^]
|
|
|
|
|
You need to perform the entire query with T-SQL as follows:
<br />
use master<br />
go<br />
execute sp_configure 'allow updates',1<br />
go<br />
reconfigure with override<br />
go<br />
drop procedure sp_who<br />
go<br />
execute sp_configure 'allow updates',0<br />
go<br />
reconfigure with override<br />
go<br />
|
|
|
|
|
thanks that worked  , thanks for your help.
"Now I guess I'll sit back and watch people misinterpret what I just said......"
Christian Graus At The Soapbox
[^]
|
|
|
|
|
Is it possible to specify the port of a server in a DSN (when it not 1433, for instance)?
|
|
|
|
|
Yes it is:
connection.ConnectionString="driver={SQL Server};server=myserver;port=5000;uid=myuser;pwd=mypassword;database=mydatabase;"
|
|
|
|
|
Does anybody know of any SQL tools that allow me to formally verify that differently structured SQL statements would result in the same result set?
Thanks,
Ian
--
Ian Darling
|
|
|
|
|
I haven't ever come across any tools like this (so if anyone knows of any tool like this I'd be interested too.)
What you can do is execute the statements into two global temp tables and then compare the temp tables with one of the numerous table diff tools out there.
|
|
|
|
|
Ian Darling wrote:
Does anybody know of any SQL tools that allow me to formally verify that differently structured SQL statements would result in the same result set?
If you are using SQL Server you can use Query Analyzer and dump the results to a file (this is a menu option). Then use WinDiff against another dataset that you have dumped to compare.
-Nick Parker
|
|
|
|
|
That's a good way, but you could also write some SQL to do it:
SELECT * FROM query1name INNER JOIN query2name ON query1name.primarykey < > qurery2name.primarykey;
If you get anything back, you know that they return different results (at least in the current situation).
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
This would only verify that the same primary keys exist but does not necessarily verify that the other fields in the rows are the same.
|
|
|
|
|
But they are returning results from the same table, so if the primary key was the same, then the results would be the same, right?
Maybe I was taking it as a given that this was so - are you talking about comparing results from different tables?
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
