| Groups | Blog | Home |
dotnet general : ASP Net.Web Applicaiton or Windows Applications
I need to get some advice from a pro or someone who encounters this situtation. Currently we are using user friendly MS Access databases for two inventory warehouses located in California and New York. Unfortunately we cannot connect the two together due to poor proformance and distance (table gets corrupted) both warehouses are separate entities, which I really wanted to make it a more enterprises level. I want to move foward and use MS SQL Server 2005 and 2008 Visual Basic.Net. instead of MS Access. I want to have the the ability to have the California Warehouse able to see what New York warehouse has in stock the same for New York to see what California has in stock. My question is should I use Windows Application or ASP Net.Web Application for the front end? What are the trade off or which is better? I want to have consisted look and able to update easily the forms. Any tips or advice will be appreciated. Thank you in advance. Cheers
Well, you've learned the hard way that Access(Jet) was never meant to be a enterprise level database. .... Here is one bit of advice. A WebApplication can show a frontend to your Jet/Access database...and a web application will communicate with the Jet/Access database as a local file. (Provided you place the mdb file on the web server). This would be (not ideal) but perhaps acceptable. A winforms application would most likely have to talk to the mdb file over the network somehow. This is what ends up killing you. Because Jet/Access is just a file sitting on a server somewhere.....it has to pull alot of data over the network just to run simple queries. If you do a join of 3 tables.......(Emp,Dept,JobTitle) for example... you pull all 3 tables and ALL rows over the network to do a query that might return 1 row. That's because Jet/Access is NOT a true RDBMS ... its a file. The JetEngine sits on the local computer. There is a way to develop a software package in a way..that's not "either/or". Check this early preview post: http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!176.entry [quoted text, click to view] "CAM" <alex_martinez@comcast.net> wrote in message news:ec%23MTtuiIHA.6136@TK2MSFTNGP03.phx.gbl... > Hello, > > I need to get some advice from a pro or someone who encounters this > situtation. Currently we are using user friendly MS Access databases > for two inventory warehouses located in California and New York. > Unfortunately we cannot connect the two together due to poor proformance > and distance (table gets corrupted) both warehouses are separate entities, > which I really wanted to make it a more enterprises level. I want to > move foward and use MS SQL Server 2005 and 2008 Visual Basic.Net. instead > of MS Access. I want to have the the ability to have the California > Warehouse able to see what New York warehouse has in stock the same for > New York to see what California has in stock. My question is should I use > Windows Application or ASP Net.Web Application for the front end? What > are the trade off or which is better? I want to have consisted look and > able to update easily the forms. Any tips or advice will be appreciated. > Thank you in advance. > > Cheers >
Thanks, but I am planning to use sql server 2005 for all the tables and
queries. What I want to know which will be better Windows Application or ASP Net.Web Application for the front end and why? Thanks you in advance. Regards, [quoted text, click to view] "sloan" <sloan@ipass.net> wrote in message news:OgDVw9ziIHA.5820@TK2MSFTNGP04.phx.gbl... > > Well, you've learned the hard way that Access(Jet) was never meant to be a > enterprise level database. > ... > Here is one bit of advice. > > A WebApplication can show a frontend to your Jet/Access database...and a > web application will communicate with the Jet/Access database as a local > file. > (Provided you place the mdb file on the web server). > > This would be (not ideal) but perhaps acceptable. > > A winforms application would most likely have to talk to the mdb file over > the network somehow. This is what ends up killing you. > Because Jet/Access is just a file sitting on a server somewhere.....it has > to pull alot of data over the network just to run simple queries. > If you do a join of 3 tables.......(Emp,Dept,JobTitle) for example... you > pull all 3 tables and ALL rows over the network to do a query that might > return 1 row. > That's because Jet/Access is NOT a true RDBMS ... its a file. The > JetEngine sits on the local computer. > > There is a way to develop a software package in a way..that's not > "either/or". > > Check this early preview post: > > http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!176.entry > > > > > > "CAM" <alex_martinez@comcast.net> wrote in message > news:ec%23MTtuiIHA.6136@TK2MSFTNGP03.phx.gbl... >> Hello, >> >> I need to get some advice from a pro or someone who encounters this >> situtation. Currently we are using user friendly MS Access databases >> for two inventory warehouses located in California and New York. >> Unfortunately we cannot connect the two together due to poor proformance >> and distance (table gets corrupted) both warehouses are separate >> entities, which I really wanted to make it a more enterprises level. I >> want to move foward and use MS SQL Server 2005 and 2008 Visual Basic.Net. >> instead of MS Access. I want to have the the ability to have the >> California Warehouse able to see what New York warehouse has in stock the >> same for New York to see what California has in stock. My question is >> should I use Windows Application or ASP Net.Web Application for the front >> end? What are the trade off or which is better? I want to have >> consisted look and able to update easily the forms. Any tips or advice >> will be appreciated. Thank you in advance. >> >> Cheers >> > >
It depends on the complexity of your UI. IMHO, You have more control over
your UI with a Windows application than you do with a web-based result. And with the new ClickOnce deployment available in .Net, you can easily deploy a WinForms application and provide incremental updates to your customers. RobinS. GoldMail.com [quoted text, click to view] "CAM" <alex_martinez@comcast.net> wrote in message
news:uc%230Sd3iIHA.4536@TK2MSFTNGP06.phx.gbl... > Thanks, but I am planning to use sql server 2005 for all the tables and > queries. What I want to know which will be better Windows Application or > ASP Net.Web Application for the front end and why? Thanks you in advance. > > Regards, > > "sloan" <sloan@ipass.net> wrote in message > news:OgDVw9ziIHA.5820@TK2MSFTNGP04.phx.gbl... >> >> Well, you've learned the hard way that Access(Jet) was never meant to be >> a enterprise level database. >> ... >> Here is one bit of advice. >> >> A WebApplication can show a frontend to your Jet/Access database...and a >> web application will communicate with the Jet/Access database as a local >> file. >> (Provided you place the mdb file on the web server). >> >> This would be (not ideal) but perhaps acceptable. >> >> A winforms application would most likely have to talk to the mdb file >> over the network somehow. This is what ends up killing you. >> Because Jet/Access is just a file sitting on a server somewhere.....it >> has to pull alot of data over the network just to run simple queries. >> If you do a join of 3 tables.......(Emp,Dept,JobTitle) for example... you >> pull all 3 tables and ALL rows over the network to do a query that might >> return 1 row. >> That's because Jet/Access is NOT a true RDBMS ... its a file. The >> JetEngine sits on the local computer. >> >> There is a way to develop a software package in a way..that's not >> "either/or". >> >> Check this early preview post: >> >> http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!176.entry >> >> >> >> >> >> "CAM" <alex_martinez@comcast.net> wrote in message >> news:ec%23MTtuiIHA.6136@TK2MSFTNGP03.phx.gbl... >>> Hello, >>> >>> I need to get some advice from a pro or someone who encounters this >>> situtation. Currently we are using user friendly MS Access databases >>> for two inventory warehouses located in California and New York. >>> Unfortunately we cannot connect the two together due to poor proformance >>> and distance (table gets corrupted) both warehouses are separate >>> entities, which I really wanted to make it a more enterprises level. >>> I want to move foward and use MS SQL Server 2005 and 2008 Visual >>> Basic.Net. instead of MS Access. I want to have the the ability to have >>> the California Warehouse able to see what New York warehouse has in >>> stock the same for New York to see what California has in stock. My >>> question is should I use Windows Application or ASP Net.Web Application >>> for the front end? What are the trade off or which is better? I want >>> to have consisted look and able to update easily the forms. Any tips or >>> advice will be appreciated. Thank you in advance. >>> >>> Cheers >>> >> >> > >
Thanks Robin
[quoted text, click to view] "RobinS" <robins@imnottelling.com> wrote in message news:QrqdnQBunuPB23janZ2dnUVZ_jidnZ2d@comcast.com... > It depends on the complexity of your UI. IMHO, You have more control over > your UI with a Windows application than you do with a web-based result. > And with the new ClickOnce deployment available in .Net, you can easily > deploy a WinForms application and provide incremental updates to your > customers. > > RobinS. > GoldMail.com > > "CAM" <alex_martinez@comcast.net> wrote in message > news:uc%230Sd3iIHA.4536@TK2MSFTNGP06.phx.gbl... >> Thanks, but I am planning to use sql server 2005 for all the tables and >> queries. What I want to know which will be better Windows Application or >> ASP Net.Web Application for the front end and why? Thanks you in >> advance. >> >> Regards, >> >> "sloan" <sloan@ipass.net> wrote in message >> news:OgDVw9ziIHA.5820@TK2MSFTNGP04.phx.gbl... >>> >>> Well, you've learned the hard way that Access(Jet) was never meant to be >>> a enterprise level database. >>> ... >>> Here is one bit of advice. >>> >>> A WebApplication can show a frontend to your Jet/Access database...and a >>> web application will communicate with the Jet/Access database as a local >>> file. >>> (Provided you place the mdb file on the web server). >>> >>> This would be (not ideal) but perhaps acceptable. >>> >>> A winforms application would most likely have to talk to the mdb file >>> over the network somehow. This is what ends up killing you. >>> Because Jet/Access is just a file sitting on a server somewhere.....it >>> has to pull alot of data over the network just to run simple queries. >>> If you do a join of 3 tables.......(Emp,Dept,JobTitle) for example... >>> you pull all 3 tables and ALL rows over the network to do a query that >>> might return 1 row. >>> That's because Jet/Access is NOT a true RDBMS ... its a file. The >>> JetEngine sits on the local computer. >>> >>> There is a way to develop a software package in a way..that's not >>> "either/or". >>> >>> Check this early preview post: >>> >>> http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!176.entry >>> >>> >>> >>> >>> >>> "CAM" <alex_martinez@comcast.net> wrote in message >>> news:ec%23MTtuiIHA.6136@TK2MSFTNGP03.phx.gbl... >>>> Hello, >>>> >>>> I need to get some advice from a pro or someone who encounters this >>>> situtation. Currently we are using user friendly MS Access databases >>>> for two inventory warehouses located in California and New York. >>>> Unfortunately we cannot connect the two together due to poor >>>> proformance and distance (table gets corrupted) both warehouses are >>>> separate entities, which I really wanted to make it a more enterprises >>>> level. I want to move foward and use MS SQL Server 2005 and 2008 Visual >>>> Basic.Net. instead of MS Access. I want to have the the ability to >>>> have the California Warehouse able to see what New York warehouse has >>>> in stock the same for New York to see what California has in stock. My >>>> question is should I use Windows Application or ASP Net.Web Application >>>> for the front end? What are the trade off or which is better? I want >>>> to have consisted look and able to update easily the forms. Any tips or >>>> advice will be appreciated. Thank you in advance. >>>> >>>> Cheers >>>> >>> >>> >> >> >
You're welcome. I have control issues, so I think you can guess which type
of application *I* use. :-) RobinS. [quoted text, click to view] "CAM" <alex_martinez@comcast.net> wrote in message
news:uCVFypEjIHA.1164@TK2MSFTNGP02.phx.gbl... > Thanks Robin > > > "RobinS" <robins@imnottelling.com> wrote in message > news:QrqdnQBunuPB23janZ2dnUVZ_jidnZ2d@comcast.com... >> It depends on the complexity of your UI. IMHO, You have more control over >> your UI with a Windows application than you do with a web-based result. >> And with the new ClickOnce deployment available in .Net, you can easily >> deploy a WinForms application and provide incremental updates to your >> customers. >> >> RobinS. >> GoldMail.com >> >> "CAM" <alex_martinez@comcast.net> wrote in message >> news:uc%230Sd3iIHA.4536@TK2MSFTNGP06.phx.gbl... >>> Thanks, but I am planning to use sql server 2005 for all the tables and >>> queries. What I want to know which will be better Windows Application >>> or ASP Net.Web Application for the front end and why? Thanks you in >>> advance. >>> >>> Regards, >>> >>> "sloan" <sloan@ipass.net> wrote in message >>> news:OgDVw9ziIHA.5820@TK2MSFTNGP04.phx.gbl... >>>> >>>> Well, you've learned the hard way that Access(Jet) was never meant to >>>> be a enterprise level database. >>>> ... >>>> Here is one bit of advice. >>>> >>>> A WebApplication can show a frontend to your Jet/Access database...and >>>> a web application will communicate with the Jet/Access database as a >>>> local file. >>>> (Provided you place the mdb file on the web server). >>>> >>>> This would be (not ideal) but perhaps acceptable. >>>> >>>> A winforms application would most likely have to talk to the mdb file >>>> over the network somehow. This is what ends up killing you. >>>> Because Jet/Access is just a file sitting on a server somewhere.....it >>>> has to pull alot of data over the network just to run simple queries. >>>> If you do a join of 3 tables.......(Emp,Dept,JobTitle) for example... >>>> you pull all 3 tables and ALL rows over the network to do a query that >>>> might return 1 row. >>>> That's because Jet/Access is NOT a true RDBMS ... its a file. The >>>> JetEngine sits on the local computer. >>>> >>>> There is a way to develop a software package in a way..that's not >>>> "either/or". >>>> >>>> Check this early preview post: >>>> >>>> http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!176.entry >>>> >>>> >>>> >>>> >>>> >>>> "CAM" <alex_martinez@comcast.net> wrote in message >>>> news:ec%23MTtuiIHA.6136@TK2MSFTNGP03.phx.gbl... >>>>> Hello, >>>>> >>>>> I need to get some advice from a pro or someone who encounters this >>>>> situtation. Currently we are using user friendly MS Access >>>>> databases for two inventory warehouses located in California and New >>>>> York. Unfortunately we cannot connect the two together due to poor >>>>> proformance and distance (table gets corrupted) both warehouses are >>>>> separate entities, which I really wanted to make it a more enterprises >>>>> level. I want to move foward and use MS SQL Server 2005 and 2008 >>>>> Visual Basic.Net. instead of MS Access. I want to have the the >>>>> ability to have the California Warehouse able to see what New York >>>>> warehouse has in stock the same for New York to see what California >>>>> has in stock. My question is should I use Windows Application or ASP >>>>> Net.Web Application for the front end? What are the trade off or >>>>> which is better? I want to have consisted look and able to update >>>>> easily the forms. Any tips or advice will be appreciated. Thank you in >>>>> advance. >>>>> >>>>> Cheers >>>>> >>>> >>>> >>> >>> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
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
| home · blog · groups | Questions? Comments? Contact the dn |