How to set up database? (1 Viewer)

andersonjond

New member
Local time
Yesterday, 20:07
Joined
Feb 28, 2005
Messages
8
I have finished creating a database - my first one. Now I don't know how to deploy it.

About 7 people will be using this database. We have decided that it won't be a multi-user database shared on the network. Each person will have their own copy.

I want to split the database into Frontend/backend. When I do this it works OK but when I copy the files to the other person's computer and try to open it, the frontend says it cannot find the tables, then it gives the path that is correct for MY computer but not for the one I am copying it onto.

How do I do it?
 
Now I don't know how to deploy it.

You have your answer embedded in your own question.

We have decided that it won't be a multi-user database shared on the network. Each person will have their own copy.

If you are not sharing then everyone has their own copy and all data sets are totally independent of one another. FE/BE is not a consideration. By the way, neither will it be a consideration that anyone can see what anyone else did. I.e. you just turned 1 DB into 7 independent DBs that diverge and never the twain (well,... whatever word like "twain" you use when you meant seven instead of two...) shall meet.

You can share a back end across the network or you can share the whole DB across the network. Or you can make replicas and try to do regular reconciliation. But just copying DBs means they become totally independent. You will have to work at revoking that independence.
 
Well, thanks for replying, I guess, but this is not helpful.

We considered the issue you raise and for the time being it is more important to get the database into everyone's hands so we can start using it. There are some time constraints at the present time that will go away later when we can address these other issues.

So we are not putting the database together the way YOU think it ought to be done, but then YOU don't know our situation. It would be more useful if I could just get an answer to the problem at hand rather than advice on how it "should have been done".

Like I said, we considered the issue and made a conscious decision to take this route knowing the alternatives.

The reason I want to deploy it as a frontend/backend copy on everyone's PC is because that way everyone can use the database while we continue to work on getting the frontend finished. then when the frontend is finished we just replace it and don't worry about dealing with the data tables.

Currently all the table structures and the main logic for data input and reporting is ready and working. The remaining functionality that needs to be finished has to do with making the database easier to use -- more "user-friendly". Everyone wants those things but they are willing to work with what we have right now because the need is pretty strong for starting to use this real soon.

And just so you understand:
A networked shared database is not always the correct solution for every situation. It just so happens that this database will be used by people who do very different things each with very different data. I structured the database in a general way so that it can be configured completly different by each user. There is no need to share data. Again, we discussed this and decided this was an appropriate choice given our current situation.

If you feel strongly that a networked, common, shared database is the only way to deploy the database, perhaps you can build it for us (at no charge, of course).

Let me know. I'll be happy to work with you.
 
Correct - the 7 copies will be independently installed, one copy on each person's PC. Currently the tables and all the data input and reports are working fine. There are a whole bunch of bells and whistles everyone wants but those are not finished. So no one wanted to wait because we really need to start using the database like this week.

So thanks for your reply. I think this will be useful information and I will do the installs/copies with this information.
 
Surely its not too difficult to have the same file structure on each PC so the BE is always in the same place? I presume each FE is in the same folder - to make it easy to find?

C:\Program Files\somewhere?

I'd just keep it as simple as possible?
 

Users who are viewing this thread

Back
Top Bottom