what are the typical issues when we want to convert applications from access
97 to access 2003.what are the scenarios that definitely need to be taken
care of ?
how do we separate the client side and the server side information in access
2003 ?

if we want to automate the entire process (say the number of such
applications is huge) what could be the best possible approaches ?

thanks and regards

This article outlines the setup issues, conversion issues, usability issues,
etc of upgrading:
Converting from Access 97
at:
http://allenbrowne.com/ser-48.html

The typical way of handling the server side and client side is to use 2 MDB
files: a back end (data) file on the server, and a front end (application)
file on each workstation. If that is a new idea, see:
Split your MDB file into data and application
at:
http://allenbrowne.com/ser-01.html
If you already have the application split, you will want to convert both the
back end and front end. If you will have some users on A97 and some on
A2003, you will need to leave the back end as an A97 file, and provide the
A2003 front end to the users who have that version.

I am not aware of a batch converter, as they are several issues to be
addressed in each database.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"sivakumar_india" <(E-Mail Removed)> wrote in
message
news:7543C938-419A-495A-BC8D-(E-Mail Removed)...
> what are the typical issues when we want to convert applications from
> access
> 97 to access 2003.what are the scenarios that definitely need to be taken
> care of ?
> how do we separate the client side and the server side information in
> access
> 2003 ?
>
> if we want to automate the entire process (say the number of such
> applications is huge) what could be the best possible approaches ?
>
> thanks and regards

thanks browne
that did help a lot

regards

"Allen Browne" wrote:

> This article outlines the setup issues, conversion issues, usability issues,
> etc of upgrading:
> Converting from Access 97
> at:
> http://allenbrowne.com/ser-48.html
>
> The typical way of handling the server side and client side is to use 2 MDB
> files: a back end (data) file on the server, and a front end (application)
> file on each workstation. If that is a new idea, see:
> Split your MDB file into data and application
> at:
> http://allenbrowne.com/ser-01.html
> If you already have the application split, you will want to convert both the
> back end and front end. If you will have some users on A97 and some on
> A2003, you will need to leave the back end as an A97 file, and provide the
> A2003 front end to the users who have that version.
>
> I am not aware of a batch converter, as they are several issues to be
> addressed in each database.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "sivakumar_india" <(E-Mail Removed)> wrote in
> message
> news:7543C938-419A-495A-BC8D-(E-Mail Removed)...
> > what are the typical issues when we want to convert applications from
> > access
> > 97 to access 2003.what are the scenarios that definitely need to be taken
> > care of ?
> > how do we separate the client side and the server side information in
> > access
> > 2003 ?
> >
> > if we want to automate the entire process (say the number of such
> > applications is huge) what could be the best possible approaches ?
> >
> > thanks and regards
>
>
>