All,

how would you handle having two persons who work on
creating/designing/editing a DB?

TIA

FYI I'm not in this situation but just in case.

Simultaneously or consecutively?

If simultaneously, one approach might be to allow both to open the same
file, but the first one on an object will 'lock' it from the other.

If consecutively, you'd need a way to ensure that PersonB doesn't start
until PersonA is done ... that's a matter of communication.

There are tools that help with the communication ...

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.


"tighe" <(E-Mail Removed)> wrote in message
news:B8CB819D-9161-4EFD-91FE-(E-Mail Removed)...
> All,
>
> how would you handle having two persons who work on
> creating/designing/editing a DB?
>
> TIA
>
> FYI I'm not in this situation but just in case.

On May 27, 4:00*pm, tighe <ti...@discussions.microsoft.com> wrote:
> All,
>
> how would you handle having two persons who work on
> creating/designing/editing a DB?
>
> TIA
>
> FYI I'm not in this situation but just in case.

About the only way this would work if the two work simultaneously is
that both work on separate front ends. I have worked on a database
while someone else (unknown to me) was changing things... You'll do
that exactly once in your life before you swear never to do it again.
If you want to merge the databases into a third (safer that way!)
later you can.

thanks for the responses.

"Piet Linden" wrote:

> On May 27, 4:00 pm, tighe <ti...@discussions.microsoft.com> wrote:
> > All,
> >
> > how would you handle having two persons who work on
> > creating/designing/editing a DB?
> >
> > TIA
> >
> > FYI I'm not in this situation but just in case.
>
> About the only way this would work if the two work simultaneously is
> that both work on separate front ends. I have worked on a database
> while someone else (unknown to me) was changing things... You'll do
> that exactly once in your life before you swear never to do it again.
> If you want to merge the databases into a third (safer that way!)
> later you can.
> .
>