Shamil Salakhetdinov
shamil at users.mns.ru
Thu Sep 29 15:11:58 CDT 2005
> there are MILLIONS of companies with 10 or fewer employees You're lucky guy, John! :) Small companies' owners here can afford luxury cars and houses but they can't afford (just do not want) to pay well for custom software development. If you'll have some custom software development work to share for your country's MILLIONS of companies I'd not mind! :) Shamil ----- Original Message ----- From: "John W. Colby" <jwcolby at colbyconsulting.com> To: "'Access Developers discussion and problem solving'" <accessd at databaseadvisors.com> Sent: Thursday, September 29, 2005 5:40 PM Subject: Re: [AccessD] The future of Access, .NET and SQL > Another thing to consider is that while there are 500 fortune 500 companies, > there are MILLIONS of companies with 10 or fewer employees, and > correspondingly smaller customer base. These small companies need low cost, > functional applications, not applications tuned for 100k hits per > minute/hour/ or even month. > > I have a client that is 5 people scattered across the country. They all > need access to their data on a single server/location. ASP.Net looks like a > good solution for that kind of application. > > John W. Colby > www.ColbyConsulting.com > > Contribute your unused CPU cycles to a good cause: > http://folding.stanford.edu/ > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence > Sent: Thursday, September 29, 2005 9:09 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] The future of Access, .NET and SQL > > > Hi Shamil: > > I agree with your assessment on ASP. Supposedly, ASP.Net 2.0 is leap > forward, if you fully believe the hype. I also know that RAD generated > applications will require a lot of fine-tuning to be able to scale up but on > the other hand I do remember the hype on Access when it first arrived. It > was a difficult and slow package but gradually it became worthy of notice. > > A lot of Access improvements were that we as developers began learn how to > optimize the package until it could support a 100 plus users. I am hoping > that ASP.Net is the next standard bearer and will be able to support a 1000 > or 10,000 plus users. Other companies are starting to develop web based > application, like the following: > (http://www.24sevenoffice.com/webpage/en/index.htm or > http://www.richercomponents.com/richtextbox/ ) and a local company and > mentor (http://www.functionfox.com ) are in the process of migrating their > application to ASP. With their single program they currently support a staff > of 10. > > Whether those apps or our apps are scalable or manageable, who knows at this > point. ...but the features are all there.... > > Jim > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil > Salakhetdinov > Sent: Thursday, September 29, 2005 12:49 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] The future of Access, .NET and SQL > > Jim, > > Did you ask the trainers how good/bad such half-generated ASP.NET > application will work on high workload of 1,000, 10,000, 100,000 etc. users? > > I did work a few with ASP.NET 1.1 but I have a colleague who have written > real apps - he says there is no way to have highly scalable ASP.NET > applications if one uses web forms with code behind etc. - one have to write > many things manually, with most of the code stripped from code behind into > compiled .dlls, fine tune caching etc.etc - only in this case one can get > highly scalable effective ASP.NET applications... > > ... I can be wrong but I think "there is no miracles in this World" - all > these great features and RAD are more marketing campaign than anything else > - a lot of work is needed to develop a real masterpiece software including > ASP.NET 2.0 based... > > ...of course "toys" web applications for not very high workload can be > developed in "toy mode" promoted by MS marketing campaign. And it may happen > this is all what is needed for many small businesses to become > "webisized"... > > ...yes, I know MS does do a lot in the area of software architecture and MS > is developing pre-built blocks but this is IMO still a long way to go until > they become really fine tuned for high workload.... > > ...and MS usually tends to solve tough tasks of "software efficiency > bottlenecks" by adding more and speedier hardware - yes, hardware is > becoming cheaper and cheaper every day but to keep up&running all that "Web > farms", "SQL Server farms" experienced system engineers are needed... > > Recap: > ====== > -VS.NET 2005 and ASP.NET 2005 - is yet another "crazy technology race > catch-up" - they promise a lot but ROI could be not as big as one may expect > it to be if any at all; > > - yes, I go this "crazy" way of course because I like VS.NET and because I > have no option to "quit to a farm here and to program just for pleasure" but > after all that years of my working in IT-industry I'd not go blind - I'd > check and stress-test all that RAD solutions MS promotes before relying on > them... > > Shamil > > ----- Original Message ----- > From: "Jim Lawrence" <accessd at shaw.ca> > To: "'Access Developers discussion and problem solving'" > <accessd at databaseadvisors.com> > Sent: Thursday, September 29, 2005 10:34 AM > Subject: Re: [AccessD] The future of Access, .NET and SQL > > > > Hi Arthur: > > > > There is an heir-apparent to the ADP and it is ASP.Net 2.0. I was down > > at Redmond in the Devscovery conference, a real three-ring circus... > > and I am not kidding. Fairly significant demo apps, can be written in > > ASP.Net 2.0, that connect to a full featured MS SQL 2003/Report-Writer > > or SQL Express, that were created using its RAD interface that only > > had a couple lines of manually enter coding. > > > > There are full user login interfaces that actually add users across > > the internet, take their email address, send a confirmation request, > > set-up an automatic call-in receipt, additionally prompt with a > > graphic user input > for > > additional security. There are full digital-signed security controls > > and many more state-of-the-art features like, ADO.Net with data > > formatted in > XML > > and standard formats, auto-synchronization (works similar to > > call-back) > and > > full distribution of static datasets. These features can all be > > generated > by > > just selecting from option lists through wizards. Anyone can create an > > application with only a good understanding of where they want to go. > > As > you > > learn more the whole boiler-plated routines can be tricked up to the > > hilt. It is all very impressive. Here is a URL to the trainers that > > gave the presentation and demos to the group at the conference: > > http://www.wintellect.com/training/courseofferings.aspx?courses=5&id=4 > > 8 > > > > I do have a full list of all the demos and if you would be interested > > I > can > > send you them, off-line. I would suggest that you sign up to their > > on-line newsletters as I have heard they can be quite helpful. > > > > HTH > > Jim > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur > > Fuller > > Sent: Wednesday, September 28, 2005 8:21 PM > > To: 'Access Developers discussion and problem solving' > > Subject: Re: [AccessD] The future of Access, .NET and SQL > > > > I have no complaint with that route. As you may know, my treasured > > partner Peter Brawley and I have described such a path (c.f. > > www.artfulsoftware.com). But that is neither here nor there. The big > problem > > with that path is that there is nothing even close to Access that > > delivers Linux apps (except as described in said e-book, using Access > > and the links to MySQL -- what I want is something like an ADP that > > hooks directly to MySQL. It isn't there. We tried in the > > aforementioned book to illustrate a way to get there, but it doesn't > > offer the same intimacy. We tried and delivered as best we could. But > > it isn't the same as ADP and there isn't a lot that we can do about > > it). > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim > > Lawrence > > Sent: September 28, 2005 7:50 PM > > To: 'Access Developers discussion and problem solving' > > Subject: Re: [AccessD] The future of Access, .NET and SQL > > > > That is a rub; through the years I have become a master at Dbase and > > its various iterations, Clipper, SuperBase, SmartWare, Advanced > > Revelation, Pascal, Fortran, FoxBase/Pro, Angoss, Access, Clarion, C > > and a few other miscellaneous environments. > > > > ...and another 3000 foot climb with dual pack-sacks and I keep > > thinking > that > > maybe I should have gone the open-source routine; Linux, Apache, MySQL > > and PHP :-) > > > > Jim > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com