//The < button in .NET framework

Recognize QR Code in .NET framework //The < button

if(currentRecordNumber > 0){

currentRecordNumber--;

showRecord(currentRecordNumber);

if(etargetequals(button2)){

if(currentRecordNumber < 4){

currentRecordNumber++;

showRecord(currentRecordNumber);

return true;

void showRecord(int recordNumber)

Element root = dgetRoot();

Element elem = null, elem2 = null;

Enumeration enum = rootgetChildren();

for(int index = 0; index <= recordNumber; index++){

elem = (Element)enumnextElement();

medicine1setText("");

medicine2setText("");

medicine3setText("");

Enumeration enum2 = elemgetChildren();

while(enum2hasMoreElements()){

elem2 = (Element)enum2nextElement();

if (elem2getTagName()equals("FIRSTNAME")) {

text1setText(elem2getText());

if (elem2getTagName()equals("LASTNAME")) {

text2setText(elem2getText());

if (elem2getTagName()equals("MEDICINE")) {

if(medicine1getText()equals("")){

medicine1setText(elem2getText());

else if(medicine2getText()equals("")){

medicine2setText(elem2getText());

else if(medicine3getText()equals("")){

medicine3setText(elem2getText());

public medicinesFrame(String str)

super (str);

public boolean handleEvent(Event evt)

switch (evtid)

case EventWINDOW_DESTROY:

dispose();

Systemexit(0);

return true;

default:

return superhandleEvent(evt);

<!DOCTYPE DOCUMENT [

That completes our exploration of XML database handling for the moment We've seen how to move through the records in a database while displaying each record's data, how to add records to a database and save the new database file, how to search through a database for a record that matches a specific criterion, and now how to handle variable-length records We've come far in this chapter In the next chapter, we'll continue our exploration of XML as we look at Part II of the XML specification[md]XML links

Copyright 1997 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use; the corporation also has a comprehensive Privacy Policy governing information we may collect from our customers

1997 The McGraw-Hill Companies, Inc All rights reserved Any use of this Beta Book is subject to the rules stated in the Terms of Use

In this chapter, we'll explore part II of the XML specification[md]XML links XML links expand the idea of the simple links you find in specifications like HTML This chapter is based on the W3C document "WD-xml-link-970731," which you can find at +; the most up-to-date version of the XML link specification may be found at http://wwww3org/TR/WD-xml-link XML can support not only the unidirectional links of HTML, but also more sophisticated multidirectional and self-describing links A multidirectional link is a link that you can move along [md]a process called traversing[md]starting at more than one of the data items that it links; these data items are called the link's resources We are going to examine the XML link specification in this chapter, including simple links, extended links, inline links, out-of-line links, keyword-driven links, extended link groups, the show and actuate link axes, and more There's a great deal coming up in this chapter, so we will start at once with an overview of XML links

As you might expect, you specify an XML link with an XML element However, unlike HTML, there is no specific XML link tag (like the <A> tag in HTML) Instead, you use the XML-LINK attribute to specify a link; this attribute can take the values +IMPLE, EXTENDED, LOCATOR, GROUP, or DOCUMENT corresponding to the various types of XML links and linking elements The actual target of the link or the link element is stored in the HREF attribute Here's an example of the simplest type of XML link, which we can model after the HTML <A> element: <A XML-LINK="SIMPLE" HREF="http://microsoftcom/">Microsoft</A>

Tip: Because XML links rely on using attributes, there may be a conflict between the attributes you are already using for a tag and the XML link attributes (which are ROLE, HREF, TITLE, SHOW, INLINE, CONTENT-ROLE, CONTENT-TITLE, ACTUATE, BEHAVIOR, and STEPS) To remove the conflict, you can rename (this process is called remapping) the XML attributes to new names, like this, where we rename the XML link TITLE attribute to XML-TITLE and the XML link attribute SHOW to XML-SHOW: <!ATTLIST DOCUMENT XML-LINK CDATA #FIXED "SIMPLE"

Simple XML links are very much like HTML links Here's how you can set up an <A> tag in a document so that it acts like an HTML link (note that you can give the tag any tag name, not just <A>, because XML checks the XML-LINK attribute to find links, not the tag name): <!ELEMENT A ANY>