Forum Moderators: open
Im learning a little C but looking for preferably an online tutorial (or a book) to learn more about ASP and SQL
Many thanks :)
A place well worth subscribing to (if you have the $$) is asptoday.com.
Also, try asp101, 4guysfromrolla.com and 15seconds.com.
Hope it helps.
Im in this one for the long term so Im thinking a book would be great :) Thanks for the suggestions hasbeen. I was looking in Amazon and found a book that included access to Wrox books, though the description went along the lines of "experienced users only"
im looking for something that will give me the basics of SQL onwards, and the way ASP can work with this
Im a beginner so one of those big thick books would be a start
If someone has a good book they know of and dont think the should post the link, please sticky it to me, im willing to pay for a good, recommended book
Without a doubt, there's benefit. But there are also the drawbacks, like dealing with the dynamic URLs that are generated. I've gathered that there's a difference in methods to overcome that, some of which depend on the platform. mod_rewrite is Apache, asp is NT/IIS
It might be worthwhile to look into that aspect of it before making an investment in books and investing time in learning. It's also a matter of how much help is available for dealing with things that come up during the learning process.
*nix/Apache can be expected to have Perl, PHP and MySQL available, but asp is not supported. I've thought of getting into asp, simply because the Basic language associated is so simple from the perspective of the programming background I have (not internet related at all), but I don't really care to be restricted to anything so proprietary.
Not being conversant in databases can be a hindrance in many ways. I asked a friend what he recommended as the best way to go, and hands down he suggested PHP and MySQL. PHP is very appealing, since code snippets can be inserted into HTML, for one thing. I've also read about some of the other benefits.
O'Reilly has terrific books, but most likely there should be a choice of which platform will be worked with from the start, before making any substantial investment, either monetarily or with time.
BoL, you might want to try one of the Wrox books entitled "Beginning Active Server Pages", then "Beginning ASP Databases". Those should give you enough to get started and then understand the sites listed above.
Also, having looked through your site I would be very easy indeed to build a database driven site without any "?"s. Having a database site does not mean having 'example.com/onepage.asp?quailfiers' by default. You can have many pages each hard coded to draw specific information out of the database thereby retaining instant control and yet making the SEs happy as well.
Go Fo It!
Onya
Woz
[4guysfromrolla.com...]
While some of their code tends to be bloated, it does work across every browser and it validates.
But it's also a quick way of generating a site and learning the code behind it. Once you get the code learned, all you need Dreamweaver for is visual layout.
I'd have to agree with the above post though regarding .Net. If you are just starting out that's probably a better solution.
As for the proprietary argument, well, there will always be that debate.
My webserver is IIS/2000 so it made sense for me to learn ASP. If I hosted with *nix I'd probably learn PhP or JSP.
Then again, you could always go straight to Java in the first place and cut out the middle man ;)
Woz Id be interested in removing the ?
PPG, whats the difference between ASP and ASP.net? I thought they were the same thing where the asp.net site provideds "add ons" or something to that extent. I am unsure
I have bought a book how to learn SQL in 3 days, which involves a little ASP. This should help me with my basic databases. Learning ASP (and .net or whatever else) Im definetely interested in.
My WYSIWYG editor refuses to allow me to change SQL statements when saving them to different pages, so writing them from scratch and using search and replace will help here (when I understand the various lines of code involved)
many thank to all so far :)
The only major difference I can see in the implementation is that in old-style ASP your page would be interpreted every time it was requested, incurring a minor performance hit. In ASP.net your page is compiled and then cached the first time its requested (much like a java servelet or .jsp page) so you get slightly better performance than with the old ASP. Also apparently there is a large set of libraries which you can access (I assume something like pre-compiled COM components). This is also similar to server-side Java, where you have access to all the Java API's. Part of learning the framework in this case is learning the support libraries so you can get the most out of he platform, again much like Java.
I really don't want to get into a MS/Java argument, its been done to death so many times. At the end of the day you should go with what your comfortable with. I do think though that one hurdle for MS web developers will be learning object oriented concepts. Once you've got these concepts you'll be able to apply them equally well to MS based web solutions or to Java. Of course with Java you're not tied into a particular OS though.
I've been brushing up on my database knowledge lately and have found this book to be very helpful: 'database design for mere mortals' by Michael J. Hernandez published by Addison Wesley. The nice thing about it is that its a general book about good practices and concepts which doesn't tie you into a particular database vendor - the majority of the examples are in MS access tho.
Hope this helps. I've a nasty feeling I've just confused things for you even more tho ;)
I do a little C at college as well as database design, so normalisation and all that comes into play when I make my site.
This performance thing you mention with old style ASP interests me. One of the first and foremost priorities with any site I make is performance/speed/bandwidth requiremends orientated
I have a plant species somewhere on this hard drive I want to get into action. It will involve many relationships between common names/genus/families etc, and get pretty complicated.
Its always a bit trial and error entering something new, but im willing to learn about the various common languages used to make sure im not doing anything the "wrong" way or the slow way :)
I remember having to copy and paste about 10000 records once. You look back after finding a program that does it for you and realise how much time you wasted.
Learning about all codes and their advantages / disadvantages can only be a good thing :) keep it coming
