Access Retirement

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I don't know this is the relevant place or not, but i need information about
Access 97 support.

Can anyone tell me till when Microsoft is going to support Access 95 and 97?
Is there any URL that i can know the timelines when and what product will be
pulled out from the Product support?

I need to upgrade few Access older version applications to the latest. Here
i need to take a call, should i upgrade to Access 2003 or migrate the
databases to SQL2K?

Please someone reply to me. You can directly mail me at
(e-mail address removed)

I need this info to convey my client before EOD today. (15th Nov, 05)

Thanks in advance for your support and sorry if i wrongly posted the msg in
a diff group.

Ram
 
Ram said:
Hi,

I don't know this is the relevant place or not, but i need
information about Access 97 support.

Can anyone tell me till when Microsoft is going to support Access 95
and 97? Is there any URL that i can know the timelines when and what
product will be pulled out from the Product support?
Click to expand...

What do you mean by support? What "most" people mean by support has already
ended for both of those products. That is that no more updates or bug fixes
will be issued.

If you mean "When will they stop working on new versions of Windows?" well
that might be for as long as you would likely care since Access 2 can still
be run on the newest versions.
I need to upgrade few Access older version applications to the
latest. Here i need to take a call, should i upgrade to Access 2003
or migrate the databases to SQL2K?
Click to expand...

Not a valid choice. An Access *application* cannot be converted to SQL
Server. You can move the Tables and Data to SQL Server, but you still need
an application to use them. In that case Access is as good a tool as any
other so you wouldn't necessarily stop using Access just because you move
the data to SQL Server.

If you have valid reasons to upgrade then I would recommend going to the
latest. If you're not in a hurry you might even want to wait for the next
version which is supposed to be a much more significant upgrade compared to
the others so far.
 
Hi,

My intension is to move the data to SQL2K and still use Access Front end
which is upgraded to Access 2000.

The purpose of going to SQL2K is, the data volumes and we are facing lot of
problems in data loss and database corruption. As an immediate fix, we'll be
migrating only data to SQL2k.

Do you have any suggestions on this approach?

Ram
 
Ram said:
Hi,

My intension is to move the data to SQL2K and still use Access Front
end which is upgraded to Access 2000.

The purpose of going to SQL2K is, the data volumes and we are facing
lot of problems in data loss and database corruption. As an immediate
fix, we'll be migrating only data to SQL2k.

Do you have any suggestions on this approach?
Click to expand...

If I were doing it I would use DTS to import the tables and data to the SQL
Server, set up all of the relationships, constraints, triggers, etc., that I
need and then take a copy of my Access file, delete all of the links to the
Jet back end and then create links to the tables on the server and see how
things work.

Depending on how you built the app in the first place you might need a small
amount of additional work to get satisfactory behavior and performance or
you might need LOTS of rework to achieve that. Generally, the best
practices for a networked and shared Jet back end translate nicely to the
best practices for a client server setup. Often though the Jet application
was poorly considered from a networking standpoint and considerable rework
is required once moving the tables to a server back end.

When making the transition job 1 is to make the app work as well as it did
before the move. In many cases that is not too difficult. In order to
really take advantage of the server back end and make the application run
*better* than before can take a lot more, but that can be done on an
incremental basis once job 1 has been accomplished.
 
Back
Top