DayZd Jugg
I began programming in Assembler language, even before learning BASIC. I was pretty good at it for someone with no formal education on the subject. As a result though, programming in anything but a text editor confuses the heck out of me. As background info, I quit programming for 15 years and focused on networking. I did well and am busy doing that work now along with my HTML/ASP/VBScript/JScript/SQL programming work that keeps me fairly busy. I've been exposed to .NET programming via the Visual Studio program, but have had no training on it and going back to the start of this question, I am confused by the objects. As it is right now, I program in notepad and only use Frontpage to write tables and do other layout so I can basically verify that my tables are not missing any simple </td>'s, etc.
I suppose my question is that I would like to move out of VBScript and into a more robust language, but I don't understand all the dragging and dropping. It's just too simplistic or something. I think I'm confused by the ease of it, maybe? I don't know. In any event, I don't really care what modern language I have to learn, I just want to learn something new. Is there a tutorial out there somewhere that explains using the manufacturer's shell like Microsoft's Visual Studio that explains EVERYTHING leaving NOTHING to be assumed? One of my biggest gripes about tutorials is that they always make the assumption that you understand dragging a data connection to a specific location in a code page. I hate that. I don't get the dragging a data connection. I'm used to placing my conditional data connection in the global.asa file and calling it to use when I code a recordset.
Anyway, I am beginning to think I'm an idiot. I can't make heads or tails out of Visual Studio.
Answer
go to www.asp.net and watch the videos on either vb.net or C#.net they will walk you thru everything if you have a cd burner or a dvd burner i would burn it to a dvd and watch it on the tv and do it on your computer at the same time or what i first did before doing that is a lot of pausing and trying it out on my own after watching it!!! but it really works it's improved my skills and knowledge so much once you get the basics down then you can work your way on to other harder stuff and once you get Visual Studio most compliers work the same way so the hard part is just understanding one then the rest is just logic
go to www.asp.net and watch the videos on either vb.net or C#.net they will walk you thru everything if you have a cd burner or a dvd burner i would burn it to a dvd and watch it on the tv and do it on your computer at the same time or what i first did before doing that is a lot of pausing and trying it out on my own after watching it!!! but it really works it's improved my skills and knowledge so much once you get the basics down then you can work your way on to other harder stuff and once you get Visual Studio most compliers work the same way so the hard part is just understanding one then the rest is just logic
How can I convert VBA code to VBScript? Any Internet wizards to do this?
Myra
Hello, I need to convert some VBA code to VB script code for the following project. I am using an Access 2003 Database with an HTML webpage and my goal is to pass values to the webpage to display the database "Search Results". The page doesn't have to be published, just run from my local computer. ANY help is appreciated!
Answer
For the most part, it boils down to removing variable types and using late binding.
For example:
Dim daoDBEngine As New DAO.DBEngine
Dim daoDB As DAO.Database
Set daoDB = daoDBEngine.OpenDatabase(MyAccessFile)
becomes:
Dim daoDBEngine
Dim daoDB
Set daoDBEngine = CreateObject("DAO.DBEngine")
Set daoDB = daoDBEngine.OpenDatabase(MyAccessFile)
And:
Dim sVal As String
Dim iVal As Integer
becomes:
Dim sVal
Dim iVal
You'll want to check your variables before using them (at least those that you allow a user to specify--always a good rule, anyway). There's no guarantee that what you think stores a number is actually a number. Functions like IsNull() and IsObject() and IsNumeric() all come in handy.
Many consider it important to use some form of Hungarian notation, so that the name of the variable tells you what data that variable will hold. (Strings begin with "str" or "s", Dates begin with "dt", Integers with "int" or "i", Long values with "lng" or "l"... There are guides out there, or make your own system that fits you well, or just forget about the whole concept. :) )
There are some changes in procedures and syntax, as well, but those are fairly minor. See the link below for more info on which language supports what.
For the most part, it boils down to removing variable types and using late binding.
For example:
Dim daoDBEngine As New DAO.DBEngine
Dim daoDB As DAO.Database
Set daoDB = daoDBEngine.OpenDatabase(MyAccessFile)
becomes:
Dim daoDBEngine
Dim daoDB
Set daoDBEngine = CreateObject("DAO.DBEngine")
Set daoDB = daoDBEngine.OpenDatabase(MyAccessFile)
And:
Dim sVal As String
Dim iVal As Integer
becomes:
Dim sVal
Dim iVal
You'll want to check your variables before using them (at least those that you allow a user to specify--always a good rule, anyway). There's no guarantee that what you think stores a number is actually a number. Functions like IsNull() and IsObject() and IsNumeric() all come in handy.
Many consider it important to use some form of Hungarian notation, so that the name of the variable tells you what data that variable will hold. (Strings begin with "str" or "s", Dates begin with "dt", Integers with "int" or "i", Long values with "lng" or "l"... There are guides out there, or make your own system that fits you well, or just forget about the whole concept. :) )
There are some changes in procedures and syntax, as well, but those are fairly minor. See the link below for more info on which language supports what.
Powered by Yahoo! Answers
Comments :
Post a Comment