MSDN Magazine August 2000
View Complete Post
Microsoft .NET introduces a new suite of XML APIs built on industry standards such as DOM, XPath, XSD, and XSLT. The .NET Framework XML classes also include innovations that offer convenience, better performance, and a more familiar programming model, tightly coupled with the new .NET data access APIs-ADO.NET. XmlWriter, XmlReader, and XmlNavigator classes and classes that derive from them, including XMLTextReader and XMLTextWriter, encapsulate a number of functionalities that previously had to be accomplished manually. A discussion of the XMLDOM-Document is also included.
MSDN Magazine January 2001
Building on the browser-based org chart featuring VML (Vector Markup Language) described previously in Microsoft Internet Developer, this article takes you through the process of refining that sample app by using XML, XSL, and JScript code to create a new, improved version. Drag and drop editing is added to the org chart interface thanks to built-in support found in Internet Explorer 5.0. XML and JScript allow data manipulated on the screen to be saved back to the server in its native format. The final product of this combination of XML, XSL, and VML is a high performance, scalable Internet app that uses processing on the client to reduce stress for the server.
Scott Howlett and Jeff Dunmall
MSDN Magazine March 2000
I have a web page that displays a listing of links. A treeview control displays a hierarchy of tags with checkboxes that act as filters... when checked, the list is 'filtered'. This all works fine but what I really need is for this page to be lightning fast. Right now, checking a box fires an event and a postback, etc. I'm wondering if there is a way to do all of this on the client side. For example, could you start out with a complete listing (dataset) of all possible hyperlinks, and then apply filters to that list all on the client side so as to eliminate any lag/postback?
Ok, this is more a general question regarding an Access Database built using SQL.... Can someone please advise me. Its's my understanding that in Access, you can manipulate data contained within fields by exporting the data to Excel, manipulating the
data contained within the fields and then cutting and pasting the data directly back into Access (providing none of the field parameters are changed, merely the data contained within the fields), so that the records are updated.
I want to know if this principle still applies if the Access Database has been written using SQL please?