Re: BD Constant Updates (Design)
- From: "Antonio via AccessMonster.com" <u11740@uwe>
- Date: Thu, 27 Oct 2005 09:26:05 GMT
John, thanks for your advice.
Here's the thing: I forgot to mention that I already have the database split.
Data is on one DB and front-end on another. All the users access the front
end through the same DB, shared in a Network Drive. Thing is, I'm developing
as we speak and I have to ask people to exit the database all the time...
Is there a way to update forms, reports, modules, etc.. without asking users
to close the frontend?
Thanks
Antonio
John Vinson wrote:
>>Hi,
>>
>[quoted text clipped - 7 lines]
>>Thanks
>>Antonio
>
>Split the database.
>
>Use Tools... Database Utilities... Database Splitter Wizard to split
>the database into a "backend", containing the tables, and a Frontend
>containing all the user interface stuff. The backend should be on a
>shared drive; each user should have their own copy of the frontend,
>linked to it.
>
>You can then develop new features to your heart's content, and when
>you are ready, simply have the users delete their database and replace
>it with the latest version.
>
> John W. Vinson[MVP]
--
Message posted via http://www.accessmonster.com
.
- Follow-Ups:
- Re: BD Constant Updates (Design)
- From: John Vinson
- Re: BD Constant Updates (Design)
- From: Alex Dybenko
- Re: BD Constant Updates (Design)
- References:
- BD Constant Updates (Design)
- From: Antonio via AccessMonster.com
- Re: BD Constant Updates (Design)
- From: John Vinson
- BD Constant Updates (Design)
- Prev by Date: Re: access developers extensions
- Next by Date: Re: BD Constant Updates (Design)
- Previous by thread: Re: BD Constant Updates (Design)
- Next by thread: Re: BD Constant Updates (Design)
- Index(es):
Relevant Pages
|