<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
Hmm - Jim, I keep some old stuff on some old machines because some of my
clients and family are still using the old stuff. I have WP 5.1 and 6.1
for DOS on my old 486. If you need any documents read and translated to
a newer version, let me know. I'll be glad to convert them for a more recent
program. I have WordPerfect up to 8 for Windows and Word up to XP - so let
me know. Respond off-list if you like.<br>
<br>
Oh, and BTW, my computer science degree also required COBOL, RPG, and BASIC,
as well as C - I had to go learn Java on my own!<br>
<br>
Tina<br>
<br>
Hale, Jim wrote:<br>
<blockquote type="cite"
cite="mid869379ABF177D4118D3100508B5EF87306978016@corp-es00">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator"
content="MS Exchange Server version 5.5.2654.45">
<title>RE: [AccessD] Future of Access?</title>
<p><font size="2">The saving grace is that any new technology will be forced
to provide a migration path for the mainstream technologies it is replacing.
The trick becomes to not get too many versions behind so that you are orphaned.
For example, last night I needed to open some old wp and wpd files. Nothing
on my machine recognized them. Word will import wordperfect 5.x - anything
before then and I am sol.</font></p>
<p><font size="2">Jim Hale </font> </p>
<p><font size="2">-----Original Message-----</font> <br>
<font size="2">From: Drew Wutka [<a href="mailto:DWUTKA@marlow.com">mailto:DWUTKA@marlow.com</a>]</font>
<br>
<font size="2">Sent: Wednesday, July 16, 2003 9:46 AM</font> <br>
<font size="2">To: 'Access Developers discussion and problem solving'</font>
<br>
<font size="2">Subject: RE: [AccessD] Future of Access?</font> </p>
<br>
<p><font size="2">30 years is quite a long time. This issue has definitely
been discussed</font> <br>
<font size="2">before. The real problem with using Access 97 isn't the
.mdb nor Jet, it's</font> <br>
<font size="2">the Access GUI itself. If you build an Access 97 .mdb,
that just holds data</font> <br>
<font size="2">(so it's only tables), then it will last as long as the
OSes available keep</font> <br>
<font size="2">themselves within their current paradigm. Using VB as a
Front End thus</font> <br>
<font size="2">allows an installable (again, as long as the OSes.....)
FE, that won't need</font> <br>
<font size="2">to be replaced.</font> </p>
<p><font size="2">Creating an App entirely within Access 97 runs some other
risks. I wouldn't</font> <br>
<font size="2">really be concerned about A97 acting up with an OS, my big
concern would be</font> <br>
<font size="2">it acting up with a newer version of Office, that may come
down the road.</font> <br>
<font size="2">Everything so far has been backwards compatible, but who
knows.</font> </p>
<p><font size="2">The big issue with OS paradigms, is that right now all
available options</font> <br>
<font size="2">work in the current OS schemes. However, if the OS paradigm
changes (like</font> <br>
<font size="2">they go with some sort of virtual reality OS, or whatever),
more then likely</font> <br>
<font size="2">Access 97 will not work correctly, but then again, neither
will any other</font> <br>
<font size="2">option....because if things really shift, EVERYTHING will
need to shift with</font> <br>
<font size="2">it. Make sense?</font> </p>
<p><font size="2">It's kind of like saying that you need to build a car
that will last for 30</font> <br>
<font size="2">years. If you could build it so that all of the parts involved
truly lasted</font> <br>
<font size="2">30 years, with no need to repair anything, your limiting
factor is still</font> <br>
<font size="2">gasoline (which the car will run on.....just like Access
'runs on' an OS</font> <br>
<font size="2">like Windows 2000, XP, 9x, etc.). In 30 years, gasoline
may be completely</font> <br>
<font size="2">replaced by a new fuel source. How could you possibly build
a car with an</font> <br>
<font size="2">unknown future on the fuel? You can't, you can only guarantee
something</font> <br>
<font size="2">from with a set of defined rules. However, if gasoline
is replaced in 30</font> <br>
<font size="2">years, your car is probably going to be the least of everyone's
concerns,</font> <br>
<font size="2">since everyone will need to change to the new system. Make
sense? To try</font> <br>
<font size="2">and relate it to cars and fuel again, imagine SQL Server
2000 is the latest</font> <br>
<font size="2">model Porshe. Now imagine that Access 97 is a 1969 VW Bug.
A lot of</font> <br>
<font size="2">experts will state that the latest model Porshe has all
sorts of wonderful</font> <br>
<font size="2">features, how it can do things that weren't dreamed of in
1969. Their</font> <br>
<font size="2">right. However, right now, both cars would run on gasoline.
If gasoline</font> <br>
<font size="2">disappeared, and was replaced with a different fuel source,
both cars would</font> <br>
<font size="2">need an overhaul to run on the new fuel (OS).</font> </p>
<p><font size="2">Drew</font> </p>
<p><font size="2">-----Original Message-----</font> <br>
<font size="2">From: Foote, Chris [<a
href="mailto:Chris.Foote@uk.thalesgroup.com">mailto:Chris.Foote@uk.thalesgroup.com</a>]</font>
<br>
<font size="2">Sent: Wednesday, July 16, 2003 4:04 AM</font> <br>
<font size="2">To: '<a class="moz-txt-link-abbreviated" href="mailto:accessd@databaseadvisors.com">accessd@databaseadvisors.com</a>'</font> <br>
<font size="2">Subject: [AccessD] Future of Access?</font> </p>
<br>
<br>
<p><font size="2">Hello all!</font> </p>
<p><font size="2">I'm in the process of putting together a document for
my company. We are</font> <br>
<font size="2">bidding for a contract that will last for at least 30 years.
I'm proposing</font> <br>
<font size="2">the use of an existing database created using A97 to manage
one aspect of</font> <br>
<font size="2">this contract. I suspect that Access 97 will not be supported
(or indeed</font> <br>
<font size="2">supportable) come 2033. I need to put in some upgrade path.
I'm thinking</font> <br>
<font size="2">along the lines of:</font> </p>
<p><font size="2">A97 upgrade to A2k in the next few years.</font> <br>
<font size="2">A2k to SQL(?) in 2005</font> <br>
<font size="2">Then what?</font> </p>
<p><font size="2">Anyone got a hotline to the future?</font> </p>
<p><font size="2">Is SAP going to be the next big thing or .NET or XML
or....?</font> </p>
<p><font size="2">Any comments gratefully received.</font> </p>
<p><font size="2">I appreciate that predicting the death of Access on databaseadvisors.com
is</font> <br>
<font size="2">a bit OT >;O</font> </p>
<p><font size="2">Best regards!</font> <br>
<font size="2">Chris Foote</font> <br>
<font size="2">_______________________________________________</font> <br>
<font size="2">AccessD mailing list</font> <br>
<font size="2"><a class="moz-txt-link-abbreviated" href="mailto:AccessD@databaseadvisors.com">AccessD@databaseadvisors.com</a></font> <br>
<font size="2"><a
href="http://databaseadvisors.com/mailman/listinfo/accessd"
target="_blank">http://databaseadvisors.com/mailman/listinfo/accessd</a></font>
<br>
<font size="2">Website: <a href="http://www.databaseadvisors.com"
target="_blank">http://www.databaseadvisors.com</a></font> <br>
<font size="2">_______________________________________________</font> <br>
<font size="2">AccessD mailing list</font> <br>
<font size="2"><a class="moz-txt-link-abbreviated" href="mailto:AccessD@databaseadvisors.com">AccessD@databaseadvisors.com</a></font> <br>
<font size="2"><a
href="http://databaseadvisors.com/mailman/listinfo/accessd"
target="_blank">http://databaseadvisors.com/mailman/listinfo/accessd</a></font>
<br>
<font size="2">Website: <a href="http://www.databaseadvisors.com"
target="_blank">http://www.databaseadvisors.com</a></font> </p>
<pre wrap="">
<hr width="90%" size="4">
_______________________________________________
AccessD mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AccessD@databaseadvisors.com">AccessD@databaseadvisors.com</a>
<a class="moz-txt-link-freetext" href="http://databaseadvisors.com/mailman/listinfo/accessd">http://databaseadvisors.com/mailman/listinfo/accessd</a>
Website: <a class="moz-txt-link-freetext" href="http://www.databaseadvisors.com">http://www.databaseadvisors.com</a>
</pre>
</blockquote>
<br>
</body>
</html>