|
How can i produce an xml file from a given schema. data in the xml file should be filled from the database and the xml file should be according to the schema eg.
Schema:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="medgivande">
<xs:complexType>
<xs:attribute name="personorgnr" type="xs:positiveInteger" use="required"/>
</xs:complexType>
</xs:element>
</xs:schema>
XML File:
<?xml version="1.0" encoding="ISO-8859-1"?>
<medgivande>
<medgivande personorgnr="2143544" >
<medgivande>
something like this. data "2143544" will be fetched from the data and will be written when the xml file is created.
can someone tell me how i can do this. its urgent.
|
|
|
|
|
A schema is not supposed to be used to create an XML file. You should write code to create your XML file, using the schema as a guide.
Christian
I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
|
|
|
|
|
Thanx, but If i have a dataset with some values then can i produce xml file with the same format.
|
|
|
|
|
Simple - you've given an XML file that follows this ( simple ) Schema. So, use an XmlTextWriter to create a document that looks the same, given the data. You'd need to iterate over the rows in the dataset, using for-each, and then create the inner nodes inside the loop, opening the outer node before the loop, and closing it after.
Christian
I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
|
|
|
|
|
I won't be providing any xml file, instead i want the data in the dataset to be written to xml file. now dataset has writexml method but that won't work in this case cause the output of that xml is not what i want.
|
|
|
|
|
must...use......small.....words......only
I don't know of a way to get a dataset to write to xml using a schema. But you can create your own XML file by stepping through a dataset, and writing the nodes based on your schema.
Christian
I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
|
|
|
|
|
Thanx,
I date this girl for 2 years, and then the nagging starts: " i wanna know ur name": - Nitin
|
|
|
|
|
Hi all,
I am having a problem with a databound combobox in that when I save the record (ie, end current edit,update the database and accept the changes) the combobox resets its value back to the first object in the list.
Anyone else experienced this problem before?
My code for saving goes something like this.
'MsgBox("Record Saved")
'Create a new dataset to hold the changes that have been made to the main dataset.
Dim objDataSetChanges As Buckner_Intranet.dsNCR = New Buckner_Intranet.dsNCR
'Stop any current edits.
Me.BindingContext(DsNCR1, "NCR").EndCurrentEdit()
Me.BindingContext(Me.DsNCR1, "Responses").EndCurrentEdit()
'Get the changes that have been made to the main dataset.
objDataSetChanges = CType(DsNCR1.GetChanges, Buckner_Intranet.dsNCR)
'Check to see if any changes have been made.
If (Not (objDataSetChanges) Is Nothing) Then
Try
Me.BindingContext(Me.DsNCR1, "NCR").EndCurrentEdit()
Me.BindingContext(Me.DsNCR1, "Responses").EndCurrentEdit()
daNCR.Update(Me.DsNCR1, "NCR")
daResponses.Update(Me.DsNCR1, "Responses")
Catch eUpdate As System.Exception
MsgBox(eUpdate.Message)
End Try
'Commit the changes that were just merged
'This moves any rows marked as updated, inserted or changed to being marked as original values
DsNCR1.AcceptChanges()
End If
Cheers for any help you might be able to offer.
Kutz
_____________________
Don't take out the Magic Pen,
Don't draw on the Infinity Board
- Neil Young
|
|
|
|
|
How to use "Joins" in Crystal Reports.
Here is my query.
select books.bookid,books.bookname,issuebooks.issuedate,issuebooks.returndate,issuebooks.datereturned from books,issuebooks where books.bookid=issuebooks.bookid and memberid= '" & TextBox1.Text & "'"
I am making a report regarding to this query. How can i use this query in "crv.SelectionFormula" method, where crv is the name of the "Crystal Report Viewer" Control.
EsHbAn BaHaDuR
|
|
|
|
|
good news it can be done bad news is I dont use querys like that. In the report designer if you add the 2 database and link the like fields like a user ID or a author name they will show the information form both databases.
second to do the selectionformula call the like id from one of the fields I would use the one with the most fields called from it.
use the fllowing
CrystalReportViewer1.SelectionFormula ="{Customer.Cust_No } = " & CInt(txtCustNo.Text)
for string you have to use
CrystalReportViewer1.SelectionFormula ="{Customer.Cust_Name } = ' " & CInt(txtCustNo.Text) & "'"
you can put anything where txtCustno.text i normally name my strings and put them there.
James Kennelly
|
|
|
|
|
I currently have an application that uses System.Web.Mail to send mail to our Exchange server using SMTP. The problem is that our new virus scanner (McAfee) blocks port 25 on the workstations, which prevents my applicaiton from sending email. The workaround is to have a dedicated workstation that runs this application, and leave it without virus protection, but that's not the optimal solution.
Is there a way that I can access the Exchange server directly using .NET? Outlook doesn't seem to have a problem sending emails, so there must be a way to do it. I don't need access to all of the Exchange functionality or information - I just want to provide some credentials to log into the server (even trusted authentication will work) and then be able to send outgoing mail. Any thoughts?
|
|
|
|
|
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwebmailsmtpmailclasstopic.asp
Try
SmtpMail.SmtpServer = "your mail server name goes here"
SmtpMail.Send(Message)
Catch ehttp As System.Web.HttpException
Console.WriteLine("0", ehttp.Message)
Console.WriteLine("Here is the full error message")
Console.Write("0", ehttp.ToString())
End Try
|
|
|
|
|
Thanks for the quick response, but this was the method I was using before, and it is stopped in its tracks by the new virus scanner.I get the following error message:
---> System.Runtime.InteropServices.COMException (0x80040213): The transport failed to connect to the server.
This method appears to use port 25 to connect to the mail server, and so doesn't avoid my problem. In order to bypass the virus scanner, I'm going to need to connect to the Exchange server another way. Can I use the Exchange functionality, or is there some way that I can use IMAP to send mail without a 3rd-party tool?
BTW - the code that's used in that knowledgebase article appears to be incorrect - It displays lines to the console with only the "0" instead of the actual error. The correct syntax to display the detailed error information from your example would be:
Console.WriteLine("{0}", ehttp.Message)
Console.WriteLine("Here is the full error message")
Console.Write("{0}", ehttp.ToString())
|
|
|
|
|
Ryan,
yes I see the error, thanks.
Looks like your only other option is imap, there is a C# library here on CP:
http://www.codeproject.com/csharp/IMAPLibrary.asp
I don't think it includes the create/send messages functions ect. but it will give you an idea how imap works and you can go on from there.
Hope this helps.
|
|
|
|
|
http://www.ddj.com/documents/s=8903/ddj1112722336208/20050405b.html
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
|
|
|
|
|
Yeah, but only for a fee. *dance* Ding dong, the witch is dead.....
Christian
I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
|
|
|
|
|
Dance? Did someone say dance?
![Jig | [Dance]](https://www.codeproject.com/script/Forums/Images/jig.gif)
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Why are you in the VB forum? 
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
|
|
|
|
|
Because the .NET framework means I can answer a lot of questions here ( and maybe even save a few from the dark side )
Christian
I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
|
|
|
|
|
Christian Graus wrote:
save a few from the dark side
What in this example is the dark side? (In the case of the dark side being VB .Net - ouch! )
Anyways, my main question is, what is the CodeProject forum code for the dancing dude?
Thanks,
Programmer2k4
My sig:
"And it is a professional faux pas to pay someone else to destroy your computer when you are perfectly capable of destroying it yourself." - Roger Wright
I now use my CodeProject Blog!
Most recent blog post: April 3
|
|
|
|
|
Programmer2k4 wrote:
In the case of the dark side being VB .Net
See - deep down, you DO know. 
Programmer2k4 wrote:
Anyways, my main question is, what is the CodeProject forum code for the dancing dude?
*grin* If I knew, I'd have used it. I used to know all that stuff, but I've since forgotten.
BTW - did you ever respond to my comments to your post about VB.NET in the soapbox ? I was genuinely interested in your reply to my comments.
Christian
I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
|
|
|
|
|
VB6 had it's share of problems. But so does the NET framework. NET is full of holes, inconsistencies, etc. It has just as many evils as VB 6 had, they are just different ones now.
One thing you could say for VB6, that certainly is not true for NET - you could deliver a fully functional application over the web in a reasonable size download without forcing the user to have to also download a 20+MB framework!!!
Robert
|
|
|
|
|
rwestgraham wrote:
NET is full of holes, inconsistencies, etc.
Where do you believe this to be the case ? ( serious question )
rwestgraham wrote:
It has just as many evils as VB 6 had, they are just different ones now.
I find this less likely, but by all means, enlighten me.
rwestgraham wrote:
One thing you could say for VB6, that certainly is not true for NET - you could deliver a fully functional application over the web in a reasonable size download without forcing the user to have to also download a 20+MB framework!!!
Yeah, that much is true. The Achilles heel of .NET is the framework for modem users, at least in the short term. Once everyone has it, it won't matter anymore, obviously.
Christian
I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
|
|
|
|
|
Well let me say that ADO.NET is indeed a vast improvement. Security is also nice - something we did not have at all in VB6. There are definitely some advantages to NET. And in general, I am in fact gradualy moving towards developing all my applications on NET. But I'm still using VB6 too, as are many developers.
But I'm still not all that impressed with many aspects of NET. If I put VB6 beside VB.NET I don't exactly see a lump of coal and a diamond. I see two different rocks.
I'll address the questions you pose. Not in the same order, but I think by the end I cover the issues raised.
First let me rebut some of the common arguments against VB6. The most common one favored by VB bashers was that it was not an "OOP" language because it did not support inheritence. This is a favorite argument but one of highly questionable validity.
VB6 did not support inheritencve, but it did support interface implementation.
So let's consider what some of the great minds of OOP have said. Gamma et al used mainly C++ and SmallTalk. Both support inheritence. But Gamma et al also explicitly stated that interface programming was always the preferred method because it allowed looser coupling, and that inheritence should be avoided when possible. Apparantly a lot of the people who rabidly attacked the OOP capabilities of VB6 also never bothered to study the classics of the OOP methodolgy they professed to rever.
And some of the great minds of Microsoft technology, most notably Matthew Curland have also pointed out that inheritence was a practice full of pitfalls and also best avoided.
Now, the real OOP issue with VB6 in terms of OOP was never the constant drivel of VB bashers about no inheritence, That was just the party propaganda mantra repeated ad nauseum by VB haters. The real OOP flaw in VB6 was the lack of support for true constructors/destructors. But a skilled programmer could mitigate most of these issues in VB6 by use of factory methods.
So basically, in terms of the core programming of classes - business objects, the most important single area of code implementation - NET offers only minor improvements - real constructors. But VB6 was also quite capable of supporting the majority of classical OOP methodologies and design patterns in the hands of a skilled programmer.
Now, in terms of true flaws of VB6: many inconsistencies in the GUI controls properties and implementations.
NET has the same problem. They inherit from the same basic classes but the derived classes frequently do not implement expected properties.
Just a few examples off the top of my head:
--------------------------------------------------------------------------------------------------------
The Button, CheckBox, and RadioButton all derive from the common ButtonBase base class. However the CheckBox does NOT support the PerformClick method.
The ComboBox does not support the TextLength property, even though it does support other properties for text manipulation in it’s textbox area which are common to the TextBox control.
NumericUpDown does not support wrapping. The DomainUpDown supports wrapping.
Why not? Of course, obviously these are not major issues. But it is still the same sort of inconsistent implementation of controls we had in VB6. Not critical, but very annoying.
But here is one that sucks: Tab Page Visible property has no effect. Many applications have dialogs that expose certain options on Tab Pages but not others depending on the user's privilige levels. In VB NET we cannot just hide the tabs accordingly., By virtue of inheritence from thed base Control class, a Visible property is exposed. It's there, it just does not work. And I can see no technical reason why it should not.
--------------------------------------------------------------------------------------------------------
While you may consider these minor issues, what I am trying to point out is this basic issue:
Is it not the fundamental basis of having the framework that inheritence creates a consistent programming interface, with some derived classes having extended functionality? So why these inconsistencies?
It is anti-thetical to the entire framework concept and certainly points out that the Microsoft implementation of the framework or at least parts of it, is flawed at even basic levels of functionality.
Next notable VB6 flaw - the P&D Wizard: No features. Everything installed from a single package.
Compare to the VS.NET Setup: Windows Installer supports features, which are an important part of a multi-component complex professional install. But VS NET Setups do not support their implementation. Everything still gets lumped into a single "feature", just like with thew old P&D package. Brilliant! Just Brilliant!
So let's summarize here and see where we are so far in terms of platform comparison:
1) Programming business objects is primarily the product of the developer not the platform. True for all languages. Designing robust, maintainable, extendable business object classes required developer skill in VB6 and still requires comparable developer skill in NET. Net result? (bad pun Realistically, little has changed.
2) Programming a GUI in VB6 meant dealing with inconsistent control implmentations. Programming a GUI in VB.NET means dealing with inconsistent control implementations. NET is probabaly a little better, but nothing to write home to Mom about. Plus there is the learning curve of having to discover and circumvent a new set of inconsistencies. Things have changed, maybe a little for the better, but the framework controls are hardly the consistent animals they should be based upon the concept of a framework platform.
3) Setup Projects? Different, not neccessarily better. At least you could pretty easily hack the VB6 setup project to create "Feature" style installs. Try manually editing an MSI created from VS.NET!! Hope you have a lot of time on your hands.
Now lets' consider the real "evils" I perceive in NET:
1) Biggest by far is startup time. Even with native images. The framework takes a long time to load, and you cannot even get up a splash screen before it does. Vb6 could pop up a splash screen in less than a second then you coould do your initialization. Not so in NET. Way too slow at startup. Keep in mind that the tytpical developers powerhouse is a few lightyears ahead of the typical box the vast majority of users have sitting in their cubicle. Net apps load noticeably slow on my machine. On the basic business aqpp grunt user's computer, the speed which a NET app loads is probably better described as "glacial".
2) The framework size. we agree on this. But we may not agree on how long "short term" really is. I assume you consider short term as "soon". For the subset of "everyone" that falls in the domain of my concern, I consider "once everyone has it" as nowhere in the immediately foreseeable future. Not this year. Not next year.
I work in healthcare. Many small doctor's offices are using Win98 still. Convincing them to change applications is tough, but doable if you have a good product. Convincing them to change their entire platform is another matter altogether. Users are not developers. And despite what many developers might think, you might be surprised by how long it really will be before most users are running platforms with NET framework already installed. And doctors almost always only have a dialup because that is the standard way they submit their claims. They are not paying for DSL or Broadband so the nurses can surf the web. If they have to downoad the framework, and most will, you can forget it. It ain't gonna happen. That forces you to distrbute NET applications to this sector on media. That means creating media, creating professional looking media with logo printed CDs, physical distribution. It is not a minor issue by any measn.
3) Stability. I've used Visual Studio 6 for years. It crashed occasionally because I was hacking some program like writing threads in VB6 or subclassing. So I restarted it. But I never fatally crashed VS6. I NEVER had to uninstall VS6 and reinstall it because something stopped working. NEVER!
Look at this forum. There is an entire group on this forum dedicated to problems with the NET IDE. I personally have had my NET IDE fail in some unrecoverable fashion twice. Why? Because of I downloaded friggin Internet Explorer service pack patches and updates. An Internet Explorer service pack corrupts my VS NET IDE? What's up with that?
If the NET IDE itself is so fragile, and obviously it is, based not only on my experience but hundreds of others, why should I be confident of anything about the framework stability on a client's machine?
Maybe the framework is more stable. But the only evidence I have is that the IDE stability is just plain sh*tty. What can I deduce about the stability of the framework? Nothing really. Hopefully MS put more emphasis on stability of the framework. Maybe that would explain why they apparantly put so little effort into the stability of the IDE.
But a sh*tty IDE does not exactly make me tend to believe the framework stability is rock solid.
And many if not most development products end up being released late. But NET's original release was not late, it was really, really late. That generally always implies a lot of hurry-scurry last minute QFEs to get the product out. 1.1 certainly fixed some of those. But I think it is safe to assume that a lot of bugs were also carried over from 1.0. That hardly inspires confidence in stability.
I could go on, but ....
You know it's a lot like the TV commercials. The drug ad where the guy says: "When people say something is better, you'd want proof, right?"
Well, I see a lot of people who really love to hate Vb6. The same people generally rant and rave about NET being better. Sorry. I think it's based on personal basis more than anything. I want proof. Show me the money ...
Robert
|
|
|
|
|
rwestgraham wrote:
Now, in terms of true flaws of VB6: many inconsistencies in the GUI controls properties and implementations.
No, I don't count that as a major flaw of VB6/VB.NET, at least my lengthy list did not include this, or anything about inheritance.
rwestgraham wrote:
Tab Page Visible property has no effect
Really ? I'm sure it worked for me when I used tab pages in a C# application.
rwestgraham wrote:
Compare to the VS.NET Setup: Windows Installer supports features, which are an important part of a multi-component complex professional install. But VS NET Setups do not support their implementation. Everything still gets lumped into a single "feature", just like with thew old P&D package. Brilliant! Just Brilliant!
I have no time for the built in Windows Installer implimentation, it's early days and bare bones ( in VC6, they gave us a pared down version of InstallShield, from memory ). I have bought and use a 3rd party installer product ( advanced installer, FWIW )
rwestgraham wrote:
Biggest by far is startup time. Even with native images.
That's mostly the framework starting for the first time. I don't see how this is a big problem, to be honest. So your user has to wait a second for a splash screen. If you wanted speed, what were you doing in VB6 ? That's what C++ is for.
rwestgraham wrote:
I assume you consider short term as "soon".
*grin* Probably when either a killer .NET app comes along, or the version of Windows after XP is widely installed, or Microsoft include it in a service pack that has some other compelling reason for people to download.
rwestgraham wrote:
There is an entire group on this forum dedicated to problems with the NET IDE.
Yeah, but how often do people post to it ? The VS.NET IDE rarely crashes for me, and that only on a machine I know to be unstable. Even then, it doesn't crash, it simply fails to kill the process it's meant to be debugging, and freezes. I kill and restart, and it's fine.
rwestgraham wrote:
But a sh*tty IDE does not exactly make me tend to believe the framework stability is rock solid.
The IDE certainly does some things I hate, for example the time it takes to decide what errors to show me when it finishes compiling. But I regard it as stable.
rwestgraham wrote:
Well, I see a lot of people who really love to hate Vb6. The same people generally rant and rave about NET being better. Sorry. I think it's based on personal basis more than anything. I want proof. Show me the money ...
To be honest, my claim is that VB is crap, full stop, and that C# is better. So I can't really help you
It sounds like you're in the 5% of VB users who are also programmers though. Why did you move to VB.NET instead of C# ?
Christian
I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
