How do I distribute my DB

constantG

Registered User.
Local time
Today, 19:10
Joined
Jun 24, 2009
Messages
92
What's the best way to implement my database?

It has to work on a large corporate network which uses a remote infrastructure for updating software.

It will be used by a maximum of 2 people at the same time but will be available to about 30 people.
 
Last edited:
I think there-in lies the problem.. although we are all on the same network, there needs to be 4 separate databases working separately from each other.
 
I have had a eureka moment.
I must find a way of making it available to all 4 positions without compromising each position. (I think).

Please forgive me I am a little tipsy lol
 
Not sure I follow what you are saying. (Maybe I need another drink :D)

I would suggest that you read the link in my previous post. It has information on deploying your front end.

If you are needing security, I would recommend that you get the Window Logged on User and use that to authenticate the user to see if they should have permissions to the database.
 
:eek:Wow:eek: Did I really write that last night ^^^^^^^^^^^

So let me get this straight. I split the DB at the .mdb stage then make a .mde file from that. is the .mde file also split into f/e & b/e.

Then, whenever I make changes to the (now split) .mdb file I make a new .mde and share the new file with the users.

Also, there are folders associated with the DB, where do I put those?

Thanks
 
Last edited:
What's the best way to implement my database?

It has to work on a large corporate network which uses a remote infrastructure for updating software.

It will be used by a maximum of 2 people at the same time but will be available to about 30 people.

HiTechCoach already covered splitting the database.

At our office, which has several remote locations, we found that using Microsfot SQLServer to store the data provided better performance than having an Access back-end. You may be interested in SQL Server 2005 Express Edition since it is advertised as free. I have not used the Express Edition. PS: Check to make sure that your company is not already using SQL Server for other applications. If it is that should be good news.

Access is simply used as a "front end". To distribute the Access front end (as it is revised), I simply email it to the users. I should also note that each user has to then go through the process of establishing the ODBC connection.
 
Last edited:
Thanks Steve, Hitechcoach,

I think I have finally got it. I am ready to deploy and I will look into the use of sql 2005.
 
Now that you have the idea, maybe I should not dare add my comment.
The FE (Front End) and BE (Back End) are very necessary. The BE can be an Access dB, SQL Server, or other type of database. Access or SQL Server (any level) are great choices in my book. You will want one copy of this for all the FE to link to one way or another.

Then make the FE into a .mde as you said. In general, this keeps users from having access to your code among other security controls.

For distribution:
You will have better response and more consistant response if you can give each user thier own copy of the FE. If you put one FE on a network drive and have everyone try to share it, there will be resource issues. Ideally, each person is somehow distributed their own copy of the MDE that connects back to the single BE database file.

At one site, I use a 3rd party software that distributes the FE to each users's PC every time a version update is released.
At another site, I use Citrix Services to create a custom folder each time a user loggs in and the server copies the latest versionof the FE into that user's folder during the session.

Hope that helps! I am leaving on vacation in 30 minutes. And will have many drinks while fishing from the back portch.
 

Users who are viewing this thread

Back
Top Bottom