Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / July 2005

Tip: Looking for answers? Try searching our database.

Is this the correct set-up for updating files in multi-user scenar

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Amit - 14 Jul 2005 21:15 GMT
Using MS Access 2K on Windows XP

I have recently implemented a database application split into FE and BE for
the first time. I will be making modifications to the FE, and was wondering
if someone could give me feedback on the setup I have.

1. The BE is on the shared drive in a separate folder.
2. The Master FE is on the shared drive in a separate folder.
3. Each user has a copy of the FE on the C: drive, and a short-cut to the
copy on their desktop.
4. The unsplit database is in a separate folder on the shared drive.
5. I keep a copy of the unsplit database in a separate folder for making
modifications and testing.

After I make any modifications to the database,
a. I copy the unsplit database to the server,
b. Split it and replace the existing BE and Master FE,
c. Copy FE to each user's C: drive.

I'm aware that I can use an auto FE updater for c., and have been exploring
it.
If there is a better way to do the above, please let me know.

Thanks.

-Amit
Rick Brandt - 14 Jul 2005 21:20 GMT
> Using MS Access 2K on Windows XP
>
[quoted text clipped - 18 lines]
> exploring it.
> If there is a better way to do the above, please let me know.

Whoa, you replace the BE file?  What about the data that it contains?

Usually one only replaces the FE file.  If you need to occassionally make
changes to the BE then what you propose is fine if you are first kicking out
all users and importing all of the data from the old BE inot the new one.

Otherwise my only comment would be that keeping a combined file around for
further development seems to add unnecessary complexity to me.  I would just
have design copies of a split system.

Signature

I don't check the Email account attached
to this message.     Send instead to...
RBrandt    at       Hunter      dot      com

Amit - 14 Jul 2005 21:55 GMT
<snip>

> Whoa, you replace the BE file?  What about the data that it contains?

Hi Rick,

Thanks for catching that!! Phew. No, I have no intention of replacing the BE
file. I want to keep my job :)

> Usually one only replaces the FE file.  If you need to occassionally make
> changes to the BE then what you propose is fine if you are first kicking out
> all users and importing all of the data from the old BE inot the new one.

Yes, that's what I intended. I don't forsee any regular or major changes in
the BE, and I can make them when needed after getting exclusive access.

> Otherwise my only comment would be that keeping a combined file around for
> further development seems to add unnecessary complexity to me.  I would just
> have design copies of a split system.

Seems reasonable to me. I guess I was being cautious, but since keeping a
combined file is not going to make any difference, and will add another layer
of complexity, I'll do away with it.

Thanks Rick!! Much appreciated.

-Amit
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.