Access 2000 application

[scubalin]

I have an old access 2000 application that has now been called back into
service. I would like to package this program for use across the
network/teminals with run-time access.

I develop on a stand-alone XP station. Do I need Xp developer or access
2000 developer? What will do the trick?

Thanks

 

[Ed Metcalfe]

I have an old access 2000 application that has now been called back into
service. I would like to package this program for use across the
network/teminals with run-time access.

I develop on a stand-alone XP station. Do I need Xp developer or access
2000 developer? What will do the trick?

Thanks

Access 2002 and 2003 are both backwards-compatible with Access 2000 so
either should do what you want.

Ed Metcalfe.

 

[scubalin]

Access 2002 and 2003 are both backwards-compatible with Access 2000 so
either should do what you want.

Ed Metcalfe.

OK. So let me get this straight before I proceed. I have a few users that still have access 2000 on their machines. If I deploy under 2002, can they still run the packaged 2002 program without version conflict?

 

[Robert Morley]

As long as you create the database itself in Access 2000 format, everything
will be fine. I've never tried it with the run-time version of Access, but
I don't believe that will make any difference.


Rob

 

[scubalin]

Thanks so much to Rob and ED. You have both been a tremendous help. I
developed this app in 2000. It's has grown rather large over the years and
is now a bear to maintain. Nonetheless, it's quite powerful and far
surpasses the software package that we bought to replace it. Can you
recommend a good access analyzer tool that will help to maintain this beast?

My deepest gratitude,
scubalin

 

[Robert Morley]

I would suggest starting that as a topic of its own, as you'll probably get
more responses. Often people will skip messages if the more-obvious subject
is something they're not competent with, even moreso if they see that others
have already replied.


Rob