DWUTKA at marlow.com
DWUTKA at marlow.com
Wed Jun 2 12:22:31 CDT 2004
I write for both our Intranet, and for the web. I have no qualms with client side scripting on our Intranet, because it's just like you said, a controlled environment. It's going to the web that is tricky. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Christopher Hawkins Sent: Wednesday, June 02, 2004 11:59 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] VB.NET This is why I try to limit my web work to intranet apps rather than public websies - I can be 100% certain that all my users are using Browser X, which saves me from worrying if the page will render properly in Upstart v2.6x on an even-numbered Tuesday immediately preceding the equinox. I feel for you guys who write publicly-facing sites. ;) -Christopher- ---- Original Message ---- From: DWUTKA at marlow.com To: accessd at databaseadvisors.com, Subject: RE: [AccessD] VB.NET Date: Wed, 2 Jun 2004 10:23:45 -0500 >I'm curious where they get those numbers. Most people that would >have older >systems like that probably wouldn't be on sites tracking that stuff! >LOL. > >Actually, I like programming in normal ASP. ASP.NET certainly looks >interesting, but I don't really see that much of an advantage with >the types >of projects I normally do. So it's not a matter of spending 'extra' >time to >handle low end users, it's just part of the simplicity that I like >to have >with my web stuff. > >Drew > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim >Lawrence >(AccessD) >Sent: Tuesday, June 01, 2004 11:17 PM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] VB.NET > > >Drew: > >The last time I have seem statistics of the numbers of people still >using >IE4.x or older. The numbers are in the range of 0.05% or 5 for every >10,000. >Not meaning to sound heartless, but as a programmer would you spend >time or >money on designing extensive code to support that small group of >individuals? > >Jim > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of >DWUTKA at marlow.com >Sent: Tuesday, June 01, 2004 2:35 PM >To: accessd at databaseadvisors.com >Subject: RE: [AccessD] VB.NET > > >That's good to hear! I'm still leary of 'OLDER' browsers. There >are people >in this world still using Windows 95 a, with IE 3.01. (And even >older). >Did you know it is impossible to upgrade the browser from that point, >without a CD, or the cabs for a later IE? Microsoft's own website >(including the windows update site) isn't supported in that browser. > >Still gives me the heebie jeebies. I'd have to check it out myself. > What >kind of security issues are you risking, though, if you are putting >the >scripting out on the other end to send stuff through. Just another >thought >to ponder. > >Drew > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Eric Barro >Sent: Tuesday, June 01, 2004 3:45 PM >To: Access Developers discussion and problem solving >Subject: RE: [AccessD] VB.NET > > >ASP.NET code (written in either VB.NET or C#) is not browser >dependent. In >fact ASP.NET generates the appropriate javascript code for the >client side >when it renders the page. All the business logic is encapsulated in >a DLL on >the BIN folder in the web root. > >--- >Eric Barro >Senior Systems Analyst >Advanced Field Services >(208) 772-7060 >http://www.afsweb.com > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of >DWUTKA at marlow.com >Sent: Tuesday, June 01, 2004 12:46 PM >To: accessd at databaseadvisors.com >Subject: RE: [AccessD] VB.NET > > >Actually, I watched some of the ASP.Net stuff, and the only >'impressive' >feature I saw was the ability to replace .dll's that are in use. >It's an >annoyance to restart and IIS server, but it's not that difficult >really. So >it's a neat trick, but it's not making me gear up for ASP.NET. What >I >REALLY want to know about ASP.NET, is how browser dependant is it? >They had >something VERY similiar to what you see as 'features' of ASP.NET in >some >'remote' scripting language. Can't remember the exact name. >However, it >required IE, and IE only. A lot of what ASP.NET is doing, is >mimicing >features I read about a long time ago with the 'remote' scripting. >So I'm >just a bit cautious as to how 'wowie' asp tricks get. We have users >out >there with VERY old browsers....long story. > >As far as the items I disagree with: > >Haven't found Initialize/Terminate events to be 'flaky'. > >(strongly agreed with the Dim x As New comment though...pure evil. >I used >it for a while, and didn't even know about it...) > >I personally don't care to initialize variables when I'm declaring >them. To >me, that is more of a constant role, then an variable role. I >personally >prefer to declare my variables and then get to assigning them >values. I >think it helps me structure my code better. By thinking only about >what >variables I am going to need, I get a pretty good picture of the >'framework' >I am building. I find that some of my best 'code' is when I don't >have to >declare a variable 'mid stream'. (I'll declare it at top, but I mean: >'Ooops, need a variable for that...' kind of thing). > >Not sure what you really meant with the bracket syntax for functions >and >subs. > >Never found Win32 API's to be combersome. Only quirk I have ever >found are >the ones that require ByVal (which I also agree should be the >default). > >Have never found collections to be tricky to work with, and also >have not >found them to be limited either. (What limitations are you >referring too?) > >Used File I/O commands in VB pretty easily, but I think I use >slightly >different syntax/commands then what I have seen on the list. > >VB does have console support, it just can't output to it! LOL. But >if you >are writing batch files, you just need to be able to call it. ><grin> (kind >of teasing on this one, I think it would be handy too.....I think I >did find >something sometime that showed a way to create console output from >VB). > >Only real issue I have found with the services, is that the OCX does >not >allow for multi-threading. Other then that, I practically have a >'Windows >Service Project' for VB 6.0. Practically drop in place (Actually, I >usually >just grab one I built, and plop in the new code (depending on >whether it's a >timer or 'event' driven service).) > >Have never had 'unstable' issues with Multi-threading, but I will >admit that >it is somewhat a pain to implement....well, somewhat is understating >it a >little! LOL. > >Drew > >- >--- >Outgoing mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.690 / Virus Database: 451 - Release Date: 5/22/2004 > > >-- >_______________________________________________ >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 > -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com