Advice Required

[pd06498]

The database I am creating for the organisation I work for will be used by various branches in different locations. Each branch will have its own database to record details held at that location only.

Rather than me creating a database for each branch (and there may be many of them) and personalising it for each one, I want to be able to create a generic database that allows the user at each branch to enter their own information (such as location name or branch name), which will in turn populate the startup form and reports throughout the database. I want a form to popup when the location name is blank so that the user must enter the location name, then not open again unless the user needs to edit the location name (rarely).

What is the best way to do this? Will I need to add another table for that one record, and if so, how do I restrict it to one record, or is there an easier way?

I hope I have explained this clearly enough.

Any advice appreciated.

 

[ifstar]

Create a branches table -
This will hold their company details etc for that specific branch.
When you distribute it to a new branch make sure this table is blank.
When they load the database - have it doing a check on this branch table - if it finds anything then these are the details it will display on all the forms/reports etc - if not then it will pop up a screen and make them fill the details in before continuing.

It will be restricted to only one record - as it checks to see if the table is blank or not - if it is not blank then it doesn't do any additions to it.

 

[theprez]

Some things to consider to make it easier to distribute the database. Create the one record in the branch table and give it a branch name of XX.

When you open the database, check to see if Branch = "XX". If it does, open the branch form and do not let the user close the form unless Branch <> XX and it is not null. When you design the branch form, do no allow additions or deletions and turn the cylce parameter to current record.

The main reason for these suggestions is to prevent you from having to add one record and then worrying about if its the first time and do I have to add a record to the branch. The record will already be there and you can control the table with the form. I often use a Setup form that has parameters in it and this seems to work out well.

 

[pd06498]

Thanks prez

Would I be asking to much to have a look at an example?

Thanks

 

[theprez]

OK here is a sample. I used the switchboard wizard which I don't use often, but you'll get the idea. I documented the branch form. Let me know if you have other questions.