2000/XP versions aren't compatible

[Mark]

Hi,

I am trying to find out why my database isn't working
properly on two versions of Access. I have a database
which I developed in Access 2000, but when I opened it up
on a computer with XP some of the parts of the database
were not working (toggle/command buttons, subforms,
etc.). I have different computers on a network and using
different versions of Access (2000 & XP). Rather than
upgrading all the computers to XP is there a way to run my
database file (switchboard, forms, reports, etc.)
successfully on the different versions?

I would have thought that since I developed the database
on an older version (2000) I wouldn't have a problem
running the file on a newer version (XP). I know there
are probable a few ways to convert the database to work in
both 2000 & XP. One issue to keep in mind is that I have
different people using the database with different levels
of experience with computers... can I get my database to
allow using the file with both versions of Access without
any problems?

Thanks!!!
Mark

 

[Victor Delgadillo]

2000 and XP are not compatible. If you have both versions running on your
network, you would have to maintain two versions of the front-end file, one
for each version. The data file (back-end) can remain an mdb of any flavor
and need not to be changed.
What I have done here at work is to upgrade all machines to the same version
(XP) and then switch the mde to XP for everybody. In a medium to large
environment it becomes a real headache to have two versions floating
around...

--
Victor Delgadillo [MVP Access]
Miami, Florida

Consultas al grupo, asi todos nos beneficiamos.

_

 

[Van T. Dinh]

AXP should be able to use databases in A2K file format. In fact, the
default file format for AXP is actually A2K file format.

My guess is that you have the Reference Errors. For example, you database
has an earlier ADO Library in the References but the new PC with AXP has
only the later version of ADO Library.

See Douglas J. Steele's article for possible solution:

http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

 

[Victor Delgadillo]

Van, the problem is if you compile using XP, the mde will not run on A2K. I
had tons of problems until I standardized the version to all machines using
specific databases.

--
Victor Delgadillo MS-MVP Access
Miami, Florida

Mensajes a los grupos de noticia, asi todos nos beneficiamos!

 

[Van T. Dinh]

Victor

My guess was that Mark uses MDB rather than MDE and he wrote that he
designed in A2K and had problems running the database in AXP which is the
reverse of the scenario you described.

If Mark is talking about MDB, AXP should be able to open the MDB in A2K file
format and the common problem with this arrangement is the Reference Errors.

HTH
Van T. Dinh
MVP (Access)

 

[Victor Delgadillo]

Well, if he has XP on some machines, it only makes sense that he is using XP
for developing... although it's not confirmed.
Either way, having two versions of Access running the same 'developing'
(meaning constantly changing) Access files is short of a nightmare.

--
Victor Delgadillo MS-MVP Access
Miami, Florida

Mensajes a los grupos de noticia, asi todos nos beneficiamos!

 

[Larry Linson]

No, it is not necessarily any problem at all, because the default setting
for both is to save in Access 2000 format -- it is only MDEs created with
Access 2002 that can't be run by retail Access 2000; MDBs should be just
fine (as long as whoever's using 2002 doesn't use Access 2002-specific
features, e.g., Pivot Tables).

It is, of course, less trouble if everyone's using the same version at the
same SP level, but that's just not always possible. Hey, if this stuff were
all that easy, they'd be able to replace us with minimum wage temps.

Larry Linson
Microsoft Access MVP

 

[Van T. Dinh]

I have A97, A2K and AXP and I develop applications in whichever version my
client is using unless the client will be upgrading in the near future. I
also have an old machine with Windows 3.11 and Access 2 just in case (not
sure if it works now).

Sometimes, you need to have 2 or more versions of the Front-Ends since in
practice, clients do have a number of Access (and OS) versions installed in
various computers.

Nightmares??? Only for the clients when they see my invoices <g>.

 

[Van T. Dinh]

..... Hey, if this stuff were

all that easy, they'd be able to replace us with minimum wage temps.

Larry

I think we should ask Microsoft to add intentional bugs in the next version
so that we can charge even more??? <smile>

--
HTH
Van T. Dinh
MVP (Access)



news:#[email protected]...

 

[Victor Delgadillo]

Van, what does the "HTH" letters means??

--
Victor Delgadillo MS-MVP Access
Miami, Florida

Mensajes a los grupos de noticia, asi todos nos beneficiamos!

 

[Van T. Dinh]

Hope This Helps

 

[Victor Delgadillo]

Thanks!

--
Victor Delgadillo [MVP Access]
Miami, Florida

Consultas al grupo, asi todos nos beneficiamos.

_