|
|
You're in the
dotnet academic
group:vb6 or .net
dotnet academic:
Problem:
I have an application developed in excel with a lot vba controls, macros, links btw sheets, etc...The application has reached it's resource limits with excel. Opening the app. takes minutes and large matrix calculations also take a long time. Question: What would be the best method to resolve the problems above? I was thinking of rewriting the app in vb6 than upgrade it to vb.net, once I've covered the learning curve of vb.net.
Bikii,
If it is a Windows Application (which I suspect is true seeing that it's Excel), I would skip VB6 and go directly with VB .NET. Just my opinion. As far as being a good candidate to be done in VB instead of Excel, I don't know enough about the application to venture an opinion. bill burrows [quoted text, click to view] "Bikii" <anonymous@discussions.microsoft.com> wrote in message news:025b01c3ce55$e8ffdc10$a501280a@phx.gbl... > Problem: > I have an application developed in excel with a lot vba > controls, macros, links btw sheets, etc...The application > has reached it's resource limits with excel. Opening the > app. takes minutes and large matrix calculations also > take a long time. > > Question: > What would be the best method to resolve the problems > above? > > I was thinking of rewriting the app in vb6 than upgrade > it to vb.net, once I've covered the learning curve of > vb.net. > > What's the most viable solution for the problem?
[quoted text, click to view] "Bikii" <anonymous@discussions.microsoft.com> wrote in message news:025b01c3ce55$e8ffdc10$a501280a@phx.gbl... > Problem: > I have an application developed in excel with a lot vba > controls, macros, links btw sheets, etc...The application > has reached it's resource limits with excel. Opening the > app. takes minutes and large matrix calculations also > take a long time. > > Question: > What would be the best method to resolve the problems > above? > > I was thinking of rewriting the app in vb6 than upgrade > it to vb.net, once I've covered the learning curve of > vb.net. > > What's the most viable solution for the problem? I'll second Bill's advice. If you're going to VB, going directly to VB.NET will get you into the current technology directly. If the ultimate goal is .NET, going to VB6 will be a lot of effort not easily translated into .NET. Why do two translations when one will do? Of course, only you know the application well enough to make the final decision. -- Peter [MVP Academic]
Bikii,
In addition to Bill's & Peter's comments. [quoted text, click to view] > What's the most viable solution for the problem? It really depends on what the app does, and how you perceive the app whenyou are finished. When you ultimately convert the app to VB.NET will Excel still be required? Or are you taking Excel "out of the picture"? Do you need to support "any" version of Excel or is only Excel 2003 acceptable? If Excel is out of the picture I would "rewrite" the app in VB.NET 2003, VB.NET 2003 has "Tools - Upgrade Visual Basic 6 Code" that you can cut & paste your VBA code into to convert it to VB.NET. (may require professional or better version of VS.NET 2003). If Excel is still in the picture & Excel 2003 is acceptable, you may want to consider going directly to the "Visual Studio Tools for the Microsoft Office System" (VSTO), as VSTO allows you to put "code behind" Excel worksheets, similar to how your current VBA is. VSTO can be written in C# or VB.NET. http://msdn.microsoft.com/office/understanding/vsto/ If Excel 2003 is not acceptable. You may also want to consider a COM Add-in written in VB6 or VB.NET, however if I wrote it in VB6 I would leave it in VB6, as Bill & Peter suggested, converting it to VB6 for the sole purpose of converting it to VB.NET suggests more pain then gain... Hope this helps Jay [quoted text, click to view] "Bikii" <anonymous@discussions.microsoft.com> wrote in message news:025b01c3ce55$e8ffdc10$a501280a@phx.gbl... > Problem: > I have an application developed in excel with a lot vba > controls, macros, links btw sheets, etc...The application > has reached it's resource limits with excel. Opening the > app. takes minutes and large matrix calculations also > take a long time. > > Question: > What would be the best method to resolve the problems > above? > > I was thinking of rewriting the app in vb6 than upgrade > it to vb.net, once I've covered the learning curve of > vb.net. > > What's the most viable solution for the problem?
Thank you for everyone's reply.
Ultimately, I'd like to have the app. serviced by an ASP with Citrix. I am still trying to decide if I should use excel in the background to do the calculations, because with large matrix calculations of (500 rows X 60 cols) the excel calculator does it quicker than vb. Plus I'll need the ability to calculate in the middle of the matrix which is much simpler to do in excel than an array. In regards to converting from vb6 to .net...is it that difficult of a process. I plan to develop in vb6 until I take the .net course than convert what I've written in 6 to .net. Do you think this is still to cumbersome of a process? [quoted text, click to view] >-----Original Message-----
>Bikii, >In addition to Bill's & Peter's comments. > >> What's the most viable solution for the problem? >It really depends on what the app does, and how you perceive the app when >you are finished. > >When you ultimately convert the app to VB.NET will Excel still be required? >Or are you taking Excel "out of the picture"? Do you need to support "any" >version of Excel or is only Excel 2003 acceptable? > >If Excel is out of the picture I would "rewrite" the app in VB.NET 2003, >VB.NET 2003 has "Tools - Upgrade Visual Basic 6 Code" that you can cut & >paste your VBA code into to convert it to VB.NET. (may require professional >or better version of VS.NET 2003). > >If Excel is still in the picture & Excel 2003 is acceptable, you may want to >consider going directly to the "Visual Studio Tools for the Microsoft Office >System" (VSTO), as VSTO allows you to put "code behind" Excel worksheets, >similar to how your current VBA is. VSTO can be written in C# or VB.NET. > >http://msdn.microsoft.com/office/understanding/vsto/ > >If Excel 2003 is not acceptable. You may also want to consider a COM Add-in >written in VB6 or VB.NET, however if I wrote it in VB6 I would leave it in >VB6, as Bill & Peter suggested, converting it to VB6 for the sole purpose of >converting it to VB.NET suggests more pain then gain... > >Hope this helps >Jay > >"Bikii" <anonymous@discussions.microsoft.com> wrote in message >news:025b01c3ce55$e8ffdc10$a501280a@phx.gbl... >> Problem: >> I have an application developed in excel with a lot vba >> controls, macros, links btw sheets, etc...The application >> has reached it's resource limits with excel. Opening the >> app. takes minutes and large matrix calculations also >> take a long time. >> >> Question: >> What would be the best method to resolve the problems >> above? >> >> I was thinking of rewriting the app in vb6 than upgrade >> it to vb.net, once I've covered the learning curve of >> vb.net. >> >> What's the most viable solution for the problem? > > >.
I mean Application Service Provider.
I am not fimiliar with .net so I didnt know a Matrix Library existed. Sounds interesting, I'll do some research on it. Any additional info. you can provide me on it would be much appreciated. **Note(60 column matrix represents 5 yrs) Can I sum cols and rows like excel? Also change the values of entire row in the middle of the matrix (500 X 60) or change 12 cols at a time for a particular row in the matrix. The key functionality, related to users, is that when they click a spinner button to change a value, the matrix recalcs and charts/graphs associated to it refreshes in a fraction of a sec. [quoted text, click to view] >-----Original Message-----
>Bikii, >> Ultimately, I'd like to have the app. serviced by an ASP >> with Citrix. >By ASP do you mean Application Service Provider or Active Server Pages? > >As I would not use Excel with Active Server Pages. If you mean Active Server >Pages, do you mean the original ASP or ASP.NET? > >> I am still trying to decide if I should use excel in the >> background to do the calculations, because with large >> matrix calculations of (500 rows X 60 cols) the excel >> calculator does it quicker than vb. >Instead of Excel have you considered finding a Matrix Library for .NET? > >> In regards to converting from vb6 to .net...is it that >> difficult of a process. I plan to develop in vb6 until I >> take the .net course than convert what I've written in 6 >> to .net. >Its not a difficult process, its more that you may be making more then twice >the amount of work you will have to do. Again it really depends on where you >want to get to, and where you stop along the way. New York to LA via Hawaii >may not make sense, however New York to LA via Mexico City may make sense. >However a direct flight New York to LA may not really be any quicker. You >need to decide is VB6 the layover in Hawaii or Mexico City and having a stop >there really any better then the direct flight. > >Hope this helps >Jay > >"Bikii" <anonymous@discussions.microsoft.com> wrote in message >news:0a6101c3cef2$0e0cc030$a601280a@phx.gbl... >> Thank you for everyone's reply. >> >> Ultimately, I'd like to have the app. serviced by an ASP >> with Citrix. >> >> I am still trying to decide if I should use excel in the >> background to do the calculations, because with large >> matrix calculations of (500 rows X 60 cols) the excel >> calculator does it quicker than vb. >> >> Plus I'll need the ability to calculate in the middle of >> the matrix which is much simpler to do in excel than an >> array. >> >> In regards to converting from vb6 to .net...is it that >> difficult of a process. I plan to develop in vb6 until I >> take the .net course than convert what I've written in 6 >> to .net. >> >> Do you think this is still to cumbersome of a process? >> >> >> >> >> >-----Original Message----- >> >Bikii, >> >In addition to Bill's & Peter's comments. >> > >> >> What's the most viable solution for the problem? >> >It really depends on what the app does, and how you >> perceive the app when >> >you are finished. >> > >> >When you ultimately convert the app to VB.NET will Excel >> still be required? >> >Or are you taking Excel "out of the picture"? Do you >> need to support "any" >> >version of Excel or is only Excel 2003 acceptable? >> > >> >If Excel is out of the picture I would "rewrite" the app >> in VB.NET 2003, >> >VB.NET 2003 has "Tools - Upgrade Visual Basic 6 Code" >> that you can cut & >> >paste your VBA code into to convert it to VB.NET. (may >> require professional >> >or better version of VS.NET 2003). >> > >> >If Excel is still in the picture & Excel 2003 is >> acceptable, you may want to >> >consider going directly to the "Visual Studio Tools for >> the Microsoft Office >> >System" (VSTO), as VSTO allows you to put "code behind" >> Excel worksheets, >> >similar to how your current VBA is. VSTO can be written >> in C# or VB.NET. >> > >> >http://msdn.microsoft.com/office/understanding/vsto/ >> > >> >If Excel 2003 is not acceptable. You may also want to >> consider a COM Add-in >> >written in VB6 or VB.NET, however if I wrote it in VB6 I >> would leave it in >> >VB6, as Bill & Peter suggested, converting it to VB6 for >> the sole purpose of >> >converting it to VB.NET suggests more pain then gain... >> > >> >Hope this helps >> >Jay >> > >> >"Bikii" <anonymous@discussions.microsoft.com> wrote in >> message >> >news:025b01c3ce55$e8ffdc10$a501280a@phx.gbl... >> >> Problem: >> >> I have an application developed in excel with a lot vba >> >> controls, macros, links btw sheets, etc...The >> application >> >> has reached it's resource limits with excel. Opening >> the >> >> app. takes minutes and large matrix calculations also >> >> take a long time. >> >> >> >> Question: >> >> What would be the best method to resolve the problems >> >> above? >> >> >> >> I was thinking of rewriting the app in vb6 than upgrade >> >> it to vb.net, once I've covered the learning curve of >> >> vb.net. >> >> >> >> What's the most viable solution for the problem? >> > >> > >> >. >> > > > >.
Bikii,
[quoted text, click to view] > Ultimately, I'd like to have the app. serviced by an ASP By ASP do you mean Application Service Provider or Active Server Pages?> with Citrix. As I would not use Excel with Active Server Pages. If you mean Active Server Pages, do you mean the original ASP or ASP.NET? [quoted text, click to view] > I am still trying to decide if I should use excel in the Instead of Excel have you considered finding a Matrix Library for .NET?> background to do the calculations, because with large > matrix calculations of (500 rows X 60 cols) the excel > calculator does it quicker than vb. [quoted text, click to view] > In regards to converting from vb6 to .net...is it that Its not a difficult process, its more that you may be making more then twice> difficult of a process. I plan to develop in vb6 until I > take the .net course than convert what I've written in 6 > to .net. the amount of work you will have to do. Again it really depends on where you want to get to, and where you stop along the way. New York to LA via Hawaii may not make sense, however New York to LA via Mexico City may make sense. However a direct flight New York to LA may not really be any quicker. You need to decide is VB6 the layover in Hawaii or Mexico City and having a stop there really any better then the direct flight. Hope this helps Jay [quoted text, click to view] "Bikii" <anonymous@discussions.microsoft.com> wrote in message news:0a6101c3cef2$0e0cc030$a601280a@phx.gbl... > Thank you for everyone's reply. > > Ultimately, I'd like to have the app. serviced by an ASP > with Citrix. > > I am still trying to decide if I should use excel in the > background to do the calculations, because with large > matrix calculations of (500 rows X 60 cols) the excel > calculator does it quicker than vb. > > Plus I'll need the ability to calculate in the middle of > the matrix which is much simpler to do in excel than an > array. > > In regards to converting from vb6 to .net...is it that > difficult of a process. I plan to develop in vb6 until I > take the .net course than convert what I've written in 6 > to .net. > > Do you think this is still to cumbersome of a process? > > > > > >-----Original Message----- > >Bikii, > >In addition to Bill's & Peter's comments. > > > >> What's the most viable solution for the problem? > >It really depends on what the app does, and how you > perceive the app when > >you are finished. > > > >When you ultimately convert the app to VB.NET will Excel > still be required? > >Or are you taking Excel "out of the picture"? Do you > need to support "any" > >version of Excel or is only Excel 2003 acceptable? > > > >If Excel is out of the picture I would "rewrite" the app > in VB.NET 2003, > >VB.NET 2003 has "Tools - Upgrade Visual Basic 6 Code" > that you can cut & > >paste your VBA code into to convert it to VB.NET. (may > require professional > >or better version of VS.NET 2003). > > > >If Excel is still in the picture & Excel 2003 is > acceptable, you may want to > >consider going directly to the "Visual Studio Tools for > the Microsoft Office > >System" (VSTO), as VSTO allows you to put "code behind" > Excel worksheets, > >similar to how your current VBA is. VSTO can be written > in C# or VB.NET. > > > >http://msdn.microsoft.com/office/understanding/vsto/ > > > >If Excel 2003 is not acceptable. You may also want to > consider a COM Add-in > >written in VB6 or VB.NET, however if I wrote it in VB6 I > would leave it in > >VB6, as Bill & Peter suggested, converting it to VB6 for > the sole purpose of > >converting it to VB.NET suggests more pain then gain... > > > >Hope this helps > >Jay > > > >"Bikii" <anonymous@discussions.microsoft.com> wrote in > message > >news:025b01c3ce55$e8ffdc10$a501280a@phx.gbl... > >> Problem: > >> I have an application developed in excel with a lot vba > >> controls, macros, links btw sheets, etc...The > application > >> has reached it's resource limits with excel. Opening > the > >> app. takes minutes and large matrix calculations also > >> take a long time. > >> > >> Question: > >> What would be the best method to resolve the problems > >> above? > >> > >> I was thinking of rewriting the app in vb6 than upgrade > >> it to vb.net, once I've covered the learning curve of > >> vb.net. > >> > >> What's the most viable solution for the problem? > > > > > >. > >
Bikii,
I have not used any personally yet. I would search google for "Matrix Library" along with combinations of dotnet, .net, C#, VB.NET to see what I come up with. You could also search sourceforge.net for Matrix to see if there are any available there... I would expect any matrix library "worth its weight" would be able to perform the functions you ask, again I have not used any so I cannot answer specifically. Hope this helps Jay [quoted text, click to view] "Bikii" <anonymous@discussions.microsoft.com> wrote in message news:012801c3cf10$bba895c0$a501280a@phx.gbl... > I mean Application Service Provider. > > I am not fimiliar with .net so I didnt know a Matrix > Library existed. Sounds interesting, I'll do some > research on it. Any additional info. you can provide me > on it would be much appreciated. > > **Note(60 column matrix represents 5 yrs) > Can I sum cols and rows like excel? Also change the > values of entire row in the middle of the matrix (500 X > 60) or change 12 cols at a time for a particular row in > the matrix. > > > The key functionality, related to users, is that when > they click a spinner button to change a value, the matrix > recalcs and charts/graphs associated to it refreshes in a > fraction of a sec. > > > > > >-----Original Message----- > >Bikii, > >> Ultimately, I'd like to have the app. serviced by an > ASP > >> with Citrix. > >By ASP do you mean Application Service Provider or > Active Server Pages? > > > >As I would not use Excel with Active Server Pages. If > you mean Active Server > >Pages, do you mean the original ASP or ASP.NET? > > > >> I am still trying to decide if I should use excel in > the > >> background to do the calculations, because with large > >> matrix calculations of (500 rows X 60 cols) the excel > >> calculator does it quicker than vb. > >Instead of Excel have you considered finding a Matrix > Library for .NET? > > > >> In regards to converting from vb6 to .net...is it that > >> difficult of a process. I plan to develop in vb6 > until I > >> take the .net course than convert what I've written in > 6 > >> to .net. > >Its not a difficult process, its more that you may be > making more then twice > >the amount of work you will have to do. Again it really > depends on where you > >want to get to, and where you stop along the way. New > York to LA via Hawaii > >may not make sense, however New York to LA via Mexico > City may make sense. > >However a direct flight New York to LA may not really be > any quicker. You > >need to decide is VB6 the layover in Hawaii or Mexico > City and having a stop > >there really any better then the direct flight. > > > >Hope this helps > >Jay > > > >"Bikii" <anonymous@discussions.microsoft.com> wrote in > message > >news:0a6101c3cef2$0e0cc030$a601280a@phx.gbl... > >> Thank you for everyone's reply. > >> > >> Ultimately, I'd like to have the app. serviced by an > ASP > >> with Citrix. > >> > >> I am still trying to decide if I should use excel in > the > >> background to do the calculations, because with large > >> matrix calculations of (500 rows X 60 cols) the excel > >> calculator does it quicker than vb. > >> > >> Plus I'll need the ability to calculate in the middle > of > >> the matrix which is much simpler to do in excel than an > >> array. > >> > >> In regards to converting from vb6 to .net...is it that > >> difficult of a process. I plan to develop in vb6 > until I > >> take the .net course than convert what I've written in > 6 > >> to .net. > >> > >> Do you think this is still to cumbersome of a process? > >> > >> > >> > >> > >> >-----Original Message----- > >> >Bikii, > >> >In addition to Bill's & Peter's comments. > >> > > >> >> What's the most viable solution for the problem? > >> >It really depends on what the app does, and how you > >> perceive the app when > >> >you are finished. > >> > > >> >When you ultimately convert the app to VB.NET will > Excel > >> still be required? > >> >Or are you taking Excel "out of the picture"? Do you > >> need to support "any" > >> >version of Excel or is only Excel 2003 acceptable? > >> > > >> >If Excel is out of the picture I would "rewrite" the > app > >> in VB.NET 2003, > >> >VB.NET 2003 has "Tools - Upgrade Visual Basic 6 Code" > >> that you can cut & > >> >paste your VBA code into to convert it to VB.NET. (may > >> require professional > >> >or better version of VS.NET 2003). > >> > > >> >If Excel is still in the picture & Excel 2003 is > >> acceptable, you may want to > >> >consider going directly to the "Visual Studio Tools > for > >> the Microsoft Office > >> >System" (VSTO), as VSTO allows you to put "code > behind" > >> Excel worksheets, > >> >similar to how your current VBA is. VSTO can be > written > >> in C# or VB.NET. > >> > > >> >http://msdn.microsoft.com/office/understanding/vsto/ > >> > > >> >If Excel 2003 is not acceptable. You may also want to > >> consider a COM Add-in > >> >written in VB6 or VB.NET, however if I wrote it in > VB6 I > >> would leave it in > >> >VB6, as Bill & Peter suggested, converting it to VB6 > for > >> the sole purpose of > >> >converting it to VB.NET suggests more pain then > gain... > >> > > >> >Hope this helps > >> >Jay > >> > > >> >"Bikii" <anonymous@discussions.microsoft.com> wrote in > >> message > >> >news:025b01c3ce55$e8ffdc10$a501280a@phx.gbl... > >> >> Problem: > >> >> I have an application developed in excel with a lot > vba > >> >> controls, macros, links btw sheets, etc...The > >> application > >> >> has reached it's resource limits with excel. > Opening > >> the > >> >> app. takes minutes and large matrix calculations > also > >> >> take a long time. > >> >> > >> >> Question: > >> >> What would be the best method to resolve the > problems > >> >> above? > >> >> > >> >> I was thinking of rewriting the app in vb6 than > upgrade > >> >> it to vb.net, once I've covered the learning curve > of > >> >> vb.net. > >> >> > >> >> What's the most viable solution for the problem? > >> > > >> > > >> >. > >> > > > > > > >. > >
Don't see what you're looking for? Try a search.
|
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |