Different version of Access for frontend and backend.

[Squirrel]

I've developed an Access 2002 database which will be deployed with the
backend on
a server and frontend on the users' PCs. I've now been advised that new
employees will
be given laptops with Access 2003 installed and that the server software
will not be
updated. Also some of the users are using Access 2000 and some Access 2002.
My question is - will this work? There is a lack of IT support in this
department - they've
contracted with me to build a database - but I have no control over their
use of different
versions of Access. If it's going to be a complete mess it'd be great to
know that before
starting the install. I'd appreciate any advice anyone can offer as to what
I should expect.
Thank you.

Linda

[Steve Jorgensen]

On Mon, 2 Feb 2004 23:19:58 -0800, "Squirrel" <wi*****@covad.net> wrote:

I've developed an Access 2002 database which will be deployed with the
backend on
a server and frontend on the users' PCs. I've now been advised that new
employees will
be given laptops with Access 2003 installed and that the server software
will not be
updated. Also some of the users are using Access 2000 and some Access 2002.
My question is - will this work? There is a lack of IT support in this
department - they've
contracted with me to build a database - but I have no control over their
use of different
versions of Access. If it's going to be a complete mess it'd be great to
know that before
starting the install. I'd appreciate any advice anyone can offer as to what
I should expect.
Thank you.

Linda

1. It doesn't matter what version of Access is on the server or even if any
version is installed at all. The server is just hosting a shared file, and
it's the client machines that care what format it's in.

2. Access 2003 will handle Access 2000 format files just fine. You can leave
the front-end in Access 2000 format, or upgrade it as you prefer. In any
case, the links to back-end tables in Access 2000 will work fine.

Now, the only issue you might have is with the front-end, not the back-end.
Sometimes, code written with one version will only work on another version
after you unselect and reselect some references, and decompile. It's possible
you'll have to maintain at least 3 distributions of the front-end, one for the
Access 200, one for 2002, and one for 2003. You should do all development
work in the oldest version in use, so you know it doesn't rely on any newer
features not available in older versions.

That said, if you can strongly encourage them to dump Access 2000, my
experience is that reliability of VBA code will be improved. I don't have any
experience with 2003 to compare, but 2002 has proven basically stable.

[Squirrel]

Steve,

Thank you for responding to my question. I had assumed that Access had to
be installed on the server and that therefore there could be some conflict
between different versions on the server vs the users' PCs. But if it isn't
even necessary for Access to be running on the server then I can see why
there will be no conflict. And thx for the recommendations on Access
2000/2002 and maintaining different versions on the users' PCs.

Linda

"Steve Jorgensen" <no****@nospam.nospam> wrote in message
news:9b********************************@4ax.com...

On Mon, 2 Feb 2004 23:19:58 -0800, "Squirrel" <wi*****@covad.net> wrote:

I've developed an Access 2002 database which will be deployed with the
backend on
a server and frontend on the users' PCs. I've now been advised that new
employees will
be given laptops with Access 2003 installed and that the server software
will not be
updated. Also some of the users are using Access 2000 and some Access 2002.My question is - will this work? There is a lack of IT support in this
department - they've
contracted with me to build a database - but I have no control over their
use of different
versions of Access. If it's going to be a complete mess it'd be great to
know that before
starting the install. I'd appreciate any advice anyone can offer as to whatI should expect.
Thank you.

Linda

1. It doesn't matter what version of Access is on the server or even if

any version is installed at all. The server is just hosting a shared file, and it's the client machines that care what format it's in.

2. Access 2003 will handle Access 2000 format files just fine. You can leave the front-end in Access 2000 format, or upgrade it as you prefer. In any
case, the links to back-end tables in Access 2000 will work fine.

Now, the only issue you might have is with the front-end, not the back-end. Sometimes, code written with one version will only work on another version
after you unselect and reselect some references, and decompile. It's possible you'll have to maintain at least 3 distributions of the front-end, one for the Access 200, one for 2002, and one for 2003. You should do all development
work in the oldest version in use, so you know it doesn't rely on any newer features not available in older versions.

That said, if you can strongly encourage them to dump Access 2000, my
experience is that reliability of VBA code will be improved. I don't have any experience with 2003 to compare, but 2002 has proven basically stable.

[Tony Toews]

"Squirrel" <wi*****@covad.net> wrote:

Thank you for responding to my question. I had assumed that Access had to
be installed on the server and that therefore there could be some conflict
between different versions on the server vs the users' PCs. But if it isn't
even necessary for Access to be running on the server then I can see why
there will be no conflict.

The most important thing though is to ensure everyone is at the same Jet 4.0 SP
version. Different versions could lead to corruptions.

What I've done is use the various API calls available and am checking the version
number and date/time of a crucial dll, msjetxx.dll, to ensure it matches what I have
on my system. See the tips page at my website for more details including sample
code: Verify Appropriate Jet Service Pack is installed
www.granite.ab.ca\access\verifyjetsp.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Squirrel]

Tony,

thx for your advice and the link to the code. I'll be sure everyone's
system is current before installing the database.

Linda
"Tony Toews" <tt****@telusplanet.net> wrote in message
news:gi********************************@4ax.com...

"Squirrel" <wi*****@covad.net> wrote:

Thank you for responding to my question. I had assumed that Access had tobe installed on the server and that therefore there could be some conflictbetween different versions on the server vs the users' PCs. But if it isn'teven necessary for Access to be running on the server then I can see why
there will be no conflict.
The most important thing though is to ensure everyone is at the same Jet

4.0 SP version. Different versions could lead to corruptions.

What I've done is use the various API calls available and am checking the version number and date/time of a crucial dll, msjetxx.dll, to ensure it matches what I have on my system. See the tips page at my website for more details including sample code: Verify Appropriate Jet Service Pack is installed
www.granite.ab.ca\access\verifyjetsp.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm