Hello

We've just updated some of our front end clients to access 2007 and wonder
why they can no longer access our access 2000 like database with multiple
concurrent users. This worked fine with 2003. I already saw articles talking
about splitting the database but I'm almost sure we have to update the DB
version to 2007...

1- That means that Access 2003 clients will no longer have access to the DB
2- and what about the code ? Will it be converted without any error ?

....or do you have another solution ?

Thanks in advance for all your suggestions and replies
Nicolas

You do have to split your db. When done users can still use the various
front_ends from different versions. You can link the 2007 front_end to the
2000 backend.

You can try testing it working in compatibility mode. After you have split
the db open a front_end in a 2007 environment and see if it keep acting as
expected. You do have to place the db in a 'trusted location' though
otherwise code will not run.

hth
--
Maurice Ausum


"Nicolas Heyer" wrote:

> Hello
>
> We've just updated some of our front end clients to access 2007 and wonder
> why they can no longer access our access 2000 like database with multiple
> concurrent users. This worked fine with 2003. I already saw articles talking
> about splitting the database but I'm almost sure we have to update the DB
> version to 2007...
>
> 1- That means that Access 2003 clients will no longer have access to the DB
> 2- and what about the code ? Will it be converted without any error ?
>
> ...or do you have another solution ?
>
> Thanks in advance for all your suggestions and replies
> Nicolas

>Nicolas Heyer" <(E-Mail Removed)> wrote in message
>news:E3229DD7-3346-4FA6-BCDD-(E-Mail Removed)...
> Hello
>
> We've just updated some of our front end clients to access 2007 and wonder
> why they can no longer access our access 2000 like database with multiple
> concurrent users. This worked fine with 2003. I already saw articles
> talking
> about splitting the database but I'm almost sure we have to update the DB
> version to 2007...

No, the VERY REASON WHY you split is to allow different versions of
ms-access
to work on the same data at the SAME TIME.

So, splitting is the key here. The real problem here is you really don't
want access 2003 trying to run the code at the same time that access 2007 is
running that code. (however, there no problem at all to have both 2003, and
2007 OPEN THE DATA for this application.

What you need to do here is realize that you should install your software
on EACH computer. You do that with word, your accounting package, or
whatever...so, you should do the same with applications that you build.

>
> 1- That means that Access 2003 clients will no longer have access to the
> DB

No, the above is 100% incorrect.

> 2- and what about the code ? Will it be converted without any error ?

For the most part, I find things convert well when moving "up" a version. I
suggest that you continue to develop using the lowest version (a2000). Over
time when you eventually have no a2000 machines left, then you can move to
developing in a2007.

So, by splitting, you can run 2000,2003,2007 all at the SAME TIME.
Keep in mind that the back end (data) part has to be in the lowest common
version of access (in above, that would be a2000 format).

You can read the following article of mine in which it is explained why and
how you split:

http://www.members.shaw.ca/AlbertKal...plit/index.htm



--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(E-Mail Removed)