Multiple designers

[Jorge]

We have an application with Access 2000 and normally there are three
designers working simultaneously. But forms or report modifications
requires exclusive use. That force to all others users must get out of
database when a modification is required. Somebody knows how to solve
that.
Is possible for example keep tables in other better database and share
to access as link?
Somebody can recommend us other database that work as access 97 where
multiple users could make modifications simultaneously?
May be a new access version as 2002?

Thanks in advance

J. Almarza
Chile

[almish]

jo**********@hotmail.com (Jorge) wrote in message news:<16**************************@posting.google. com>...

We have an application with Access 2000 and normally there are three
designers working simultaneously. But forms or report modifications
requires exclusive use. That force to all others users must get out of
database when a modification is required. Somebody knows how to solve
that.
Yes, you need to "split" your database .mdb file into a front-end (FE)
and back-end (BE) .mdb files. Then the FE tables are linked to the
back-end (done automatically with the Database Splitter or manually
with the Linked Table Manager - both under the Tools menu).

The FE is put on each client's PC with the BE on a share that all can
access.

Now you develop the FE further (on your PC) and distribute to the
users
when appropriate.
Is possible for example keep tables in other better database and share
to access as link?
Somebody can recommend us other database that work as access 97 where
multiple users could make modifications simultaneously?
May be a new access version as 2002?

Any ODBC compliant database will work (Oracle, SQL Server, DB/2,
Informix, MySQL, etc). You'll still have the problem if you are using
a shared FE
..mdb file. Each user needs to get a copy of the FE to prevent this
problem
and to prevent corruption of the .mdb file(s).

'---------------
' John Mishefske
'---------------

[Pieter Linden]

jo**********@hotmail.com (Jorge) wrote in message news:<16**************************@posting.google. com>...

We have an application with Access 2000 and normally there are three
designers working simultaneously. But forms or report modifications
requires exclusive use. That force to all others users must get out of
database when a modification is required. Somebody knows how to solve
that.
Is possible for example keep tables in other better database and share
to access as link?
Somebody can recommend us other database that work as access 97 where
multiple users could make modifications simultaneously?
May be a new access version as 2002?

Thanks in advance

J. Almarza
Chile

I agree with Larry - split the front (all but data tables) and back
ends (data tables only), and distribute the front end. Then let each
developer play with his own copy. Then gather your pieces together.
As long as your data tables remain the same and all your other forms
exist, you should be fine.

[Steve Jorgensen]

On 21 Jul 2004 23:09:47 -0700, pi********@hotmail.com (Pieter Linden) wrote:

jo**********@hotmail.com (Jorge) wrote in message news:<16**************************@posting.google. com>...

We have an application with Access 2000 and normally there are three
designers working simultaneously. But forms or report modifications
requires exclusive use. That force to all others users must get out of
database when a modification is required. Somebody knows how to solve
that.
Is possible for example keep tables in other better database and share
to access as link?
Somebody can recommend us other database that work as access 97 where
multiple users could make modifications simultaneously?
May be a new access version as 2002?

Thanks in advance

J. Almarza
Chile

I agree with Larry - split the front (all but data tables) and back
ends (data tables only), and distribute the front end. Then let each
developer play with his own copy. Then gather your pieces together.
As long as your data tables remain the same and all your other forms
exist, you should be fine.

Also, you can use the Access Developer Edition with Visual Source Safe to make
it easier for multiple developers to work on the same application, and not
whipe out each others' changes when trying to merge.