Different version of MDAC Causing Writing to SQL 2000?

[Guest]

We had problem users not able to keep record into SQL2000 database.
FrontEND users are using Access 2003 with SP2
But couple of user also have MDAC 2.7 RTM version with SP1
And Other (8) users have MDAC 2.8 with SP2 version
We tried user to enter with very simple form which worked fiine year 2004.
Even that using that bound form to enter new record having similar problem
to lose record. So we assume that it's not problem with new form we are
using.
So we check everybody's computer.
Couple of user has MDAC 2.7 RTM version with SP1
Other (8) users have MDAC 2.8 with SP2 version I am not sure if that would
conflict to save record to database .
Also which version of MDAC you should use with SQL 2000 SP4 version
Does anyone know about this issue?
Also One user used 10mbps network cable other all use 100mb network calbe
Also if it's possible we like to use MDAC 2.7 RTM because one of user using
that MDAC 2.7RTM doesn't seem to have much problem if that's case is there
way we can downgrade from MDAC 2.8 to MDAC2.7 version?
Please let me know if any expert or Microsoft specialist who can answer this
question

Thanks

 

[Sylvain Lafontaine]

The easiest way to downgrade from MDAC 2.8 to 2.7 would be to make a full
reinstallation (and even then, I'm not totally sure what you must do with
the automated updating feature of MS). Usually - but there are exceptions -
it's suggested by MS that all people have the latest service packs.

In the case of Access, usually there is no problem with the mixing of SP if
you take the precaution of decompiling the file (either MDB or ADP) when
switching from version of service pack. You can use the /decompile switch
in a shortcut to your file or you change one of the reference - for example
you add or remove a dummy reference - in the references window in VBA.
Changing a single reference will force Access to clear all compiled modules;
something that it seems to forget when you make only a Compact/Repair.

Many people would say that it's no longer required to decompile an Access
file after switching of version of service pack but as you seem to have
problems on your side, it's probably something worthing the try.

Of course, all these users with different versions of service packs should
have their own copy of the ADP file on their local machine.

Unlike for MDB databases, an ADP project should be relatively immune to a
bad network in the case of the datas.