XML Beginner
Hi guys,
I came from VB/SQL Server background (client-server n-tier architecture).
We have a system written in VB with VB COM object connected to the SQL Server.
Now, we are trying to move away from VB (but still want to use VB COM objects)
and start using XML/XSL as an interface to move into the web based architecture.
Now, I've heard that XML is very good thing (to be honest I have not idea
why is this) and it would be recommended to be used for the next generation
web based applications (especially .NET). Since so, I have a couple of quick
questions to experts in regards to the development of XML/XSL web based applications
with MS6 (not MS.NET).
- Can I write an independant reporting application using XML/XSL interface
directly connected to the database (SQL Server or Oracle). What I mean is
if I have a couple of tables in a database, can I somehow create an instance
of the database, create a recordset, create an SQL "SELECT" statement (or
simply call a stored procedure) and get the data somehow on the screen? What
is the proper sequence would be to do this ?
- Can XML/XSL reference COM objects written in VB and use them?
- Does XML/XSL supports VB script, Java Script, HTML/CSS, ASP.
- What is the best XML/XSL book would be recommended for an experienced VB/SQL
programmer to get XML/XSL thing "up and running".
Thanks in advance, your help would be very much appreciated.
[1515 byte] By [
Alex] at [2007-11-9 15:23:21]
# 1 Re: XML Beginner
I hate to say it, but I think you are in over your head on this one. You
need to be able to crawl before you can walk, and walk before you can run,
and you are trying to skip directly to running whilst still figuring out
how to turn over in your crib.
If you don't know WHY you should be using XML/XSL for a particular application,
you are pretty much lost. You either need to find someone in your organization
who knows this stuff and is willing to guide you through it, or you need
to start with some smaller, less ambitious projects that allow you to get
your feet wet a little. It should only take you a couple of months to get
up to speed if you take this route, and that's still a whole lot better than
picking the wrong architecture and having to live with it for the next several
years.
When you look at this problem again, and you can say "Of COURSE XML/XSL is
the way to go, and here's why...", then you are ready. Maybe you'll say
"XML/XSL doesn't apply to this problem very well, and here's why..." That's
okay too.
Get a mentor. Or hire a consultant who knows XML well (if you have lots
of dough, I can suggest a few people I know). Or maybe start with something
that lets you use XML, but not XSL, then something that uses some simple
XSL but not databases. Then play around with the XML features in SQL Server
or Oracle. Then, when you have a good feel for all the different players,
you can make an educated decision on architecture.
Jason at 2007-11-11 23:30:20 >
# 2 Re: XML Beginner
Thank you very much for such a detailed suggestion. With your permission,
I shall pass it to the management.
"Jason" <jason@creative_nospam_corp.com> wrote:
>
>I hate to say it, but I think you are in over your head on this one. You
>need to be able to crawl before you can walk, and walk before you can run,
>and you are trying to skip directly to running whilst still figuring out
>how to turn over in your crib.
>
>If you don't know WHY you should be using XML/XSL for a particular application,
>you are pretty much lost. You either need to find someone in your organization
>who knows this stuff and is willing to guide you through it, or you need
>to start with some smaller, less ambitious projects that allow you to get
>your feet wet a little. It should only take you a couple of months to get
>up to speed if you take this route, and that's still a whole lot better
than
>picking the wrong architecture and having to live with it for the next several
>years.
>
>When you look at this problem again, and you can say "Of COURSE XML/XSL
is
>the way to go, and here's why...", then you are ready. Maybe you'll say
>"XML/XSL doesn't apply to this problem very well, and here's why..." That's
>okay too.
>
>Get a mentor. Or hire a consultant who knows XML well (if you have lots
>of dough, I can suggest a few people I know). Or maybe start with something
>that lets you use XML, but not XSL, then something that uses some simple
>XSL but not databases. Then play around with the XML features in SQL Server
>or Oracle. Then, when you have a good feel for all the different players,
>you can make an educated decision on architecture.
Alex at 2007-11-11 23:31:15 >
