Here is the history as I see it
VB 6 had a few sub versions
VBA (Visual Basic for applications)
VB Script (Visual Basic Script)
VBA can still be found in Microsoft Office and as a matter of interest will
also be found in the new office 2007
it has the same IDE (Development environment) as VB6 but the forms engine is
different. Non interface code is interchangeable
VB script has no forms engine and is still supported by Windows XP it's
used on a desktop or server to automate system tasks, it is also supported
in the IE and can be used in place of Java Script but you never see much of
this because it is not cross browser friendly.
Then from VB script came ASP now called classic ASP
ASP is like PHP or JSP a way of placing script code that is run at the
server into a page to allow you to write dynamic data driven pages and once
again with a few minor differences VB 6 windows application code is
interchangeable with VB script.
In 2001 Microsoft came out with the Dot Net framework that included a new
version of ASP, ASP.NET.
ASP.NET had many advantages over Classic ASP.
Classic ASP like PHP, mixes scripting code with the HTML to build the page,
you find your self using scrip to write HTML back to the browser this makes
it a little hard to see what is happening when you are trying to work on
code some one else has written as it is often mixed with up the HTML.
Also the code is not compiled rather it is passed by the server each time a
page is called.
ASP.NET provides a frame work to code against that takes care of all of the
HTML rendering, allowing the developer to work with a web page in the same
way he did with a windows application, drag a control on to a form double
click it and put code in the event you want to trap. This way of developing
is a big part of what made VB6 so popular for Windows Applications.
In your case put a text box and button on the web form and in the "one
click" event of the button put in the code to calculate the result.
ASP.NET compiles the application to a DLL bring the all advantages compiling
gives you and the code separate from the HTML.
Along with ASP.NET came a whole new version of Visual Studio including a new
version of VB (officially VB7) that fitted with the new Dot Net frame work.
VB in ASP.NET is this new language.
VB6 people soon found that unlike previous upgrades they could not easily
port their VB 6 applications to VB Dot Net and even if they could it seemed
to many like a backward step because some of the coolest features of VB 6
were gone as was every control they knew and therefore much of their code
plus some of the syntax had changed in the language.
For ASP there is no upgrade path to ASP Dot Net you just have to re write
it, (some business logic can be reused taking into account the changes to
the VB language in Dot Net)
So now you have thousands of people around the world who have 1000's of
lines of code in applications that must stay in VB6 and Classic ASP I am
one.
Microsoft have done some work in the latest of Visual Studio 2005 to
address this and they have produced documents to help you update the code
for example there is a tool that lets you "upgrade" snippets of VB6 code to
Dot Net this works better then trying to port an entire application and may
help you in this task.
So what do people do
I maintain and continue to develop several existing apps in classic ASP and
VB6.
However I start new things in VB 2005. That is a personal choice but that's
what I do.
For your choice you will need to workout if this is something that will be
updated in the future and how complex the logic routines are in the app you
are trying to replicate,
The guy who wrote it may be able to use the resources available to convert
his code to VB Dot Net 2005, If not then a classic ASP app my be what you
end up with you can run classic ASP and ASP.NET on the same server in the
same application
to use classic ASP all you need is Note Pad and IIS server built into XP
pro, there are tools for this like the script editor in Front Page.
For Dot Net you can do the same but are better off with Visual Studio or
Visual Web Developer free from
www.asp.net
I hope this information helps you.
Max
"eclipsme" <ec******@nowhere.comwrote in message
news:_t**************@bignews5.bellsouth.net...
Steve Gerrard wrote:
>"eclipsme" <ec******@nowhere.comwrote in message
news:c1*************@bignews8.bellsouth.net...
>>Thanks for the pointers Max. I will look at asp.net, though I suspect
there will be a steep learning curve.
Max is right that going to a web page is the way to go.
In addition to ASP.Net, you could also consider "regular" ASP, which came
before it.
That was more like VB6, with regular old VB scripting for the pages.
It is a learning curve either way.
Yes, I have been confused by the diff between asp and asp.net, though this
is not the place to discuss that, I suppose. But when you say 'VB
scripting', how is that different from VB? I guess I am wondering if the
guy that wrote the VB program is going to be able to provide the scripting
needed to do the calculations needed to go from the form to the report, if
I use asp.
Harvey