<html><div style='background-color:'><DIV>
<P>All the Big Guys just spent tons of cash updating their legacy stuff for Y2K - you didn't think that was a throwaway didya? If it works...it's good. Curent account is all mainframe batch /CICS with some web. Oog still do Access (me Oog)!<BR>_D<BR></P></DIV><BR><BR><BR>"Things are only free to the extent that you don't pay for them".-Don Elliker
<DIV></DIV>
<DIV></DIV>
<DIV></DIV>
<DIV></DIV>>From: "Huffman, Jarad B." <JBHUFFMAN@MDH.ORG>
<DIV></DIV>>Reply-To: Access Developers discussion and problem solving<ACCESSD@DATABASEADVISORS.COM>
<DIV></DIV>>To: "'Access Developers discussion and problem solving'" <ACCESSD@DATABASEADVISORS.COM>
<DIV></DIV>>Subject: RE: [AccessD] Future of Access?
<DIV></DIV>>Date: Wed, 16 Jul 2003 09:26:22 -0500
<DIV></DIV>>
<DIV></DIV>>two of the requirements for a BS in computer science at my local university
<DIV></DIV>>are 2 semesters of COBOL. It's still widely used, sadly.
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>Jarad Huffman
<DIV></DIV>>
<DIV></DIV>>-----Original Message-----
<DIV></DIV>>From: Hale, Jim [mailto:jim.hale@fleetpride.com]
<DIV></DIV>>Sent: Wednesday, July 16, 2003 9:18 AM
<DIV></DIV>>To: 'Access Developers discussion and problem solving'
<DIV></DIV>>Subject: RE: [AccessD] Future of Access?
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>><WHO to DIV < it if software his maintain able be going is>><IS to DIV < able are people that technology a years few every converted not>>and willing to work with?>
<DIV></DIV>>
<DIV></DIV>>My son just graduated from college with a business degree in MIS. He has had
<DIV></DIV>>the GOOD fortune to land a great job with a major insurance company. The
<DIV></DIV>>catch? He has been assigned to the mainframe maintenance team. He is
<DIV></DIV>>attempting to learn COBOL, JCL and easytrieve (?) to service apps that might
<DIV></DIV>>have been cutting edge 30 yrs ago. For someone whose total experience is
<DIV></DIV>>with object oriented programming (he is a pretty good web designer) he is
<DIV></DIV>>going nuts! Even the manuals are out of print <G>.
<DIV></DIV>>
<DIV></DIV>>Jim Hale
<DIV></DIV>>
<DIV></DIV>>-----Original Message-----
<DIV></DIV>>From: Wortz, Charles [mailto:CWortz@tea.state.tx.us
<DIV></DIV>><mailto:CWortz@tea.state.tx.us> ]
<DIV></DIV>>Sent: Wednesday, July 16, 2003 8:52 AM
<DIV></DIV>>To: Access Developers discussion and problem solving
<DIV></DIV>>Subject: RE: [AccessD] Future of Access?
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>Arthur,
<DIV></DIV>>
<DIV></DIV>>But in 30 years will the kids know how to use pencils? <GRIN>
<DIV></DIV>>
<DIV></DIV>>That is one of the reasons I told Chris to expect some conversions of
<DIV></DIV>>his software. Unless he is planning on staying on the project for the
<DIV></DIV>>next 30 years, who is going to be able to maintain his software if it
<DIV></DIV>>is not converted every few years to a technology that people are able
<DIV></DIV>>and willing to work with?
<DIV></DIV>>
<DIV></DIV>>The software does not wear out, but finding people that understand old
<DIV></DIV>>software and are willing to maintain it is very expensive. The dBase
<DIV></DIV>>applications I wrote 10-15 years ago probably still would work fine, but
<DIV></DIV>>how are you going to find anybody that understands the dBase file
<DIV></DIV>>structure and is willing to work with it? They would have to double my
<DIV></DIV>>salary if they wanted me to stick with dBase. Thus, they all have been
<DIV></DIV>>converted to Access since that is a technology that has an large labor
<DIV></DIV>>pool of developers and maintainers.
<DIV></DIV>>
<DIV></DIV>>Charles Wortz
<DIV></DIV>>Software Development Division
<DIV></DIV>>Texas Education Agency
<DIV></DIV>>1701 N. Congress Ave
<DIV></DIV>>Austin, TX 78701-1494
<DIV></DIV>>512-463-9493
<DIV></DIV>>CWortz@tea.state.tx.us
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>-----Original Message-----
<DIV></DIV>>From: Arthur Fuller [mailto:artful@rogers.com <mailto:artful@rogers.com>]
<DIV></DIV>>Sent: Wednesday 2003 Jul 16 08:16
<DIV></DIV>>To: 'Access Developers discussion and problem solving'
<DIV></DIV>>Subject: RE: [AccessD] Future of Access?
<DIV></DIV>>
<DIV></DIV>>The only technology guaranteed to be here in 2033, AFAIK, is a pencil
<DIV></DIV>>and paper :-) However, the remote users might not like the time-lag.
<DIV></DIV>>
<DIV></DIV>>Arthur
<DIV></DIV>>
<DIV></DIV>>-----Original Message-----
<DIV></DIV>>From: accessd-bounces@databaseadvisors.com
<DIV></DIV>>[mailto:accessd-bounces@databaseadvisors.com
<DIV></DIV>><mailto:accessd-bounces@databaseadvisors.com> ] On Behalf Of Foote, Chris
<DIV></DIV>>Sent: July 16, 2003 5:57 AM
<DIV></DIV>>To: 'Access Developers discussion and problem solving'
<DIV></DIV>>Subject: RE: [AccessD] Future of Access?
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>Thanks for the input Gustav!
<DIV></DIV>>
<DIV></DIV>>I'd forgotten about Oracle! I'll add that to the list of possibilities.
<DIV></DIV>>
<DIV></DIV>>The requirements are (at this stage) pretty vague, but is likely to
<DIV></DIV>>involve up to ten concurrent users on geographically remote sites. I'm
<DIV></DIV>>guessing on half a million records split between five/six main tables.
<DIV></DIV>>My current A97 db with 16k records weighs in at (FE + BE) 15MB. My
<DIV></DIV>>proposed db is not much more complicated than this.
<DIV></DIV>>
<DIV></DIV>>Thirty years ago my programming was done on a Ferranti Pegasus
<DIV></DIV>>mainframe. I had to write the programme one paper with a pencil, convert
<DIV></DIV>>it to hole on punched cards, wait for the technician to run the
<DIV></DIV>>programme and give me the paper read-out. The Pegasus (IIRC) used 60
<DIV></DIV>>thousand ECC83 valves (tubes) and had a whole building to itself. Thirty
<DIV></DIV>>years on, I've got more processing power in my cell phone!
<DIV></DIV>>
<DIV></DIV>>But my company /still/ wants me to design a database to be used for the
<DIV></DIV>>/next/ thirty years!
<DIV></DIV>>
<DIV></DIV>>Best Regards!
<DIV></DIV>>Chris Foote (UK)
<DIV></DIV>>_______________________________________________
<DIV></DIV>>AccessD mailing list
<DIV></DIV>>AccessD@databaseadvisors.com
<DIV></DIV>>http://databaseadvisors.com/mailman/listinfo/accessd
<DIV></DIV>><HTTP: accessd listinfo mailman databaseadvisors.com>
<DIV></DIV>>Website: http://www.databaseadvisors.com <HTTP: www.databaseadvisors.com>
<DIV></DIV>>
<DIV></DIV>>_______________________________________________
<DIV></DIV>>AccessD mailing list
<DIV></DIV>>AccessD@databaseadvisors.com
<DIV></DIV>>http://databaseadvisors.com/mailman/listinfo/accessd
<DIV></DIV>>Website: http://www.databaseadvisors.com
<DIV></DIV></mailto:accessd-bounces@databaseadvisors.com></mailto:artful@rogers.com></mailto:CWortz@tea.state.tx.us></div><br clear=all><hr>MSN 8 helps <a href="http://g.msn.com/8HMIENUS/2752??PS=">ELIMINATE E-MAIL VIRUSES.</a> Get 2 months FREE*.</html>