Re: Migrating from 97 to 2002+ / JET to MSDE

I know JET will be around. What I heard is that there will be no new upgrades
or versions of it. The emailing of the data is not as interactive as you
might think. It is all made easy through automation. There is a form button
for each employee which creates the email, adds the attachment and sends it
to the company. Also the company does not have a network server. What it has,
though, is an FTP site. Will that suffice as a central point to keep our data?
"Albert D.Kallal" wrote:

As a few mentioned, JET will be around for a long long time..so, I don't
know where you heard that rumor...it is incorrect...



On the other hand with such system now that includes emailing of data
files, then all kinds of data merges, it sounds like a difficult system to
use (and, if not difficult, it at least's wastes a lot of time and needs
extra more human interaction and steps then it should.). Remember, that time
wasted could be used to feed the poor, or help others...or simply increase
company efficiency.



If you move to sql server, then it seems reasonable to have each of the
clients connect OVER the internet to ONE data store. No more emailing, no
more merging....all of this time wasting would eliminated with a solution
that allows people to connect to a central system . Since users now can
email, then one has to assume they currently have access to the internet?



Perhaps now they have limited connectivity, or no high speed internet, so,
perhaps emailing is the ONLY reasonable approach you have here. (Your hands
might be tied here - but, if they have good connections, then you can use
sql server to eliminate the emailing, and merging part.).



I see no reason to migrate to sql server unless you going to use the extra
features and abilities of sql server to eliminate several steps you now use
as a result of using ms-access. And, as mentioned, ms-access is not going
away.



On the other hand, I still have clients of mine using 16+ year old FoxPro
programs written in DOS that works on a BRAND NEW machine. And, version 2.0
of ms-access, or even earlier versions of ms-access still work fine on a
brand new machine today.



Given that the track record of Microsoft is the best in the industry in
terms of past compatibility (apple for example has forced users to throw out
old software more then once in the same time period as MS track run). So, I
see little reason to worry about running a older jet based application.



In fact, if you want to, you can find a copy of the ORIGINAL spread***
written by Dan Bricklen...it is dated 1981..and ran on the FIRST ibm pc.
And, it needs pointing out that this 1981 program still runs on a BRAND NEW
machine. So, if you can run 25 year old software on a new machine, then
really, why be worried?



So, a good reason if, and when you do migrate to sql server is that of
connectivity. Sql server can feed the data to a web based interface (so, you
might build a web based interface and application for these users...and
again eliminate all of that emailing and merge stuff). Ms-access can also
connect to Sql server OVER the internet. (again, then, after a user enters
their data...they are done...no merge,...no email...they are just done!!).



So, I would only move to sql server if there are specific features of sql
server that you need (or, are WILLING to use. So, if you are not willing to
give up the clumsy email approach, then taking on sql server would likely
result in more work, more training, and more administration. If you don't
take any advantage of sql better connectivity, then you don't gain here. It
is like finally realizing that you need a LARGE delivery truck. Unless you
can use the large truck (along with the extra expertise required to run the
large truck), you are better to stick with your delivery vans.



--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
http://www.members.shaw.ca/AlbertKallal





.