Re: Working with two or more database files

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bruce (anonymous_at_discussions.microsoft.com)
Date: 09/03/04 

Date: Fri, 3 Sep 2004 09:46:23 -0700

Consider keeping the student file small in terms of number
of fields. Just name, address, etc. Reporting
information could be in another table, with a foreign key
field to match the primary key from the student table.
Once that relationship is established, you could make the
form for reporting a subform of the student form. You
could do something like having a command button on the
student form make the subform visible. Once the student
is in senior high a different command button could be
visible to show a different subform. Details aside, if
you have one student table you can link it to any number
of other tables, and you won't have to rewrite the table
when the student goes to the senior high school.
>-----Original Message-----
>Thanks for the advice - never thought of the start up
screen - I will have to
>check it out first.
>
>Alternatively I will have to restructure the database to
incorporate two
>reporting systems. There will only be about 20 to 30
users at any time but
>the reporting system for the Junior and Senior school
vary a great deal and
>the student file is going to be gigantic if I incorporate
both systems, with
>students from both junior and senior schools.
>
>"Bruce" wrote:
>
>> If you use a single startup screen to get to either
school
>> system's database, from the user's point of view either
>> choice is an entirely separate program. You are the
only
>> one who needs to know the truth. If the problem is the
>> number of concurrent users I doubt you will fix that by
>> sharing database objects between two separate files.
>> >-----Original Message-----
>> >No there isn't but the databases are reporting systems
>> for a senior and
>> >junior school respectively. The 2 school systems vary
a
>> great deal andit is
>> >easier to set up two separate databases. However,
staff
>> are invoved in both
>> >systems and would like to access both databases from
the
>> same main menu. I
>> >could re-design the table structure to incorporate
both
>> systems but I fear it
>> >may get too big to cope with all staff trying to get
>> theri reports completed
>> >at the end of each term.
>> >
>> >"Jeff Boyce" wrote:
>> >
>> >> Is there a business reason why you don't simply
import
>> the forms from B into
>> >> A?
>> >>
>> >> While it is possible to do, you'll also need to
connect
>> the data on which
>> >> the forms are based, making it available to both A
and
>> B. Again, it would
>> >> be simpler just to import the forms and do
everything
>> in A -- you probably
>> >> want a compelling need to use such a split approach.
>> >>
>> >> --
>> >> Good luck
>> >>
>> >> Jeff Boyce
>> >> <Access MVP>
>> >>
>> >>
>> >.
>> >
>>
>.
>

Quantcast