2000/2003 Upgrade?

[Guest]

I am currently working with Access2000, and maintaining an Access97 Backend,
with an Access97 front end for some users in the firm, and Access2000
frontends for users who have Access2000.

The company is going to continue having a some users with Access2000, and
some with Access97. The affordability issue is not going to go away.

I am trying to develop Data Access Pages for users who have no Access at all
on their computers. Access 2000 is clearly glitchy in terms of data access
pages. It looks like (perhaps) Access 2003 is less glitchy.

I'm trying to figure out whether I should try to convince the firm to buy me
an upgrade to Access2003, or whether that will give me so many headaches with
compatibility that I won't know what hit me.

Comments?

 

[John Vinson]

I'm trying to figure out whether I should try to convince the firm to buy me
an upgrade to Access2003, or whether that will give me so many headaches with
compatibility that I won't know what hit me.

Access2003 uses A2000 format databases BY DEFAULT (you can choose to
convert to 2002/2003 format but it's totally optional). IME it works
fine with both 2000 format databases, and linked A97 *tables* (just as
in 2000 you cannot make design changes to A97 objects, though).

Go for it.
John W. Vinson[MVP]

 

[Guest]

Thank you. This post helped me understand that I have already been upgraded
to Access 2003, though my system says Access2000, and my database is in fact
Access2000.

This is apparently why Data Access Pages created by my Access 2003 program
say that they cannot be opened in design view by my database (which seemed
very strange). It's not quite true that they won't open in design view, it's
just mostly true.

So I'm converting a copy of my working database to Access2002/03 format to
see if data access pages work any better that way.