| Home |
| Search |
| Today's Posts |
|
#9
Posted to microsoft.public.excel.programming
|
|||
|
|||
VBA vs VB vs VBA.Net
Thanks Tom!
"Tom Ogilvy" wrote: There is probably 100% compatibility going forward from xl2000 to xl2003. Both Excels use the same major version of VBA (vba 6). The article on VB.net was talking about the 2003 version of Visual Studio. It can interact with xl2003, but certainly not as transparently as VBA and is not required at all. -- Regards, Tom Ogilvy "JMB" wrote in message ... Is it correct to say VBA macros written using Excel 2000 will likely not run properly with Excel 2003 without making the necessary conversions? I think the article you referenced was pretty clear about Office 2003 using Visual Studio, but I want to double check and make sure before I tell my boss we'll have to change many of our templates when (if) the office updates their computers and are all working w/Office 2003. "John.Greenan" wrote: Migrate your VBA code base to VB.Net and write a PIA wrapper so it can be connected to Excel. Don't waste time porting VBA-VB6, VB6 is nearing end-of-life and will not be supported for that much longer. The COM addin is a fabulous technology that never seemed to get the attention that it deserved. Have a look at the following MSDN articles: http://msdn.microsoft.com/office/und...ionfromvba.asp http://msdn.microsoft.com/library/de...asp?frame=true http://msdn.microsoft.com/library/de...asp?frame=true Have a look at those and then if you have any questions just ask... -- www.alignment-systems.com "ExcelMonkey" wrote: So Tom is it correct to say that if I want to migrate my VBA Add-in into a Com Add-in then I would do so via VB 6.0? And if so, I should buy VB 6.0 and NOT Visual Basic 2005 as this is really VB.Net. Thanks EM "Tom Ogilvy" wrote: As I understand it, VB 6.0 uses VBA as its engine and adds functionality to it the same as Excel does. so VB6 is a superset of VBA although most look at VBA as a subset of VB6. Anything after around 2002 that has to do with VB and microsoft refers to the .NET technology. so VB 2005 (express) is VB.Net People use VB Script in a lot of different ways. In terms of Excel, it is probably referring to VBA. There are also several scripting languages based on subsets of VBA/VB6. -- Regards, Tom Ogilvy "ExcelMonkey" wrote in message ... I am contemplating migrating my VBA Add-in (for Excel) into a more secure product. I was assuming that I could try to migrate this over to VB 6.0 and create a COM add-in. I also have been wondering whether or not I can creat add-ins in VB.Net. I have come to realise that I am confused by some of the terminology I see and need clarification. 1) Is "VBA" - as used in Office products (Excel/Word etc) simply "VB 6.0"? 2) Is "VB Script" simply VBA code as used in VBA in Office? 3) If I purchase "Visual Basic 2005 (Express Edition)" what does this include: VB 6.0, VB.Net, both? I ask this as when you look at the products that are included in Visual Basic Studio, you do not see reference to ..Net. You see Visual Basic, C++ etc but I am not sure if this is based on the ..Net framework. And if it is, does this mean that I cannot create regu lar VB programs? Thanks EM |
Threaded Mode
