Joe, why do you have seperate tables for each project?
Since they all have exactly the same structure, this is 100% wrong way to
design a database. It is a very common mistake from people who are not used
to databases (e.g. where you night use different worksheets in Excel), but
it is not a relational database design.
Put the different projects in the one table, with an extra field to
distinguish which project this record is for.
Allen,
Thanks for responding,
I do know that using the multiple table is the worst setup, I was
wanting to do something very temporary to try some things in theory.
What I would really love to do is create one table with a column for
the projects and them assign it some ID being a name number or
something.
I would then need the data input form I created to prompt for the
project, then once selected all records entered after that point would
only be associated with that project id and never any other. Then the
user could click a button which would open a report with those records
associated with the project id and possibly
merge the name of the project as the title of the report or prompt for
the title and once created save that title in the header and allow the
report to be amended without re-prompting for the title.
I have a few other concerns,
the db would not be stored in one location, each person would have
thier own copy, working on thier own projects, which at times I would
have to make changes and edit the information, so that would be
difficult to send remotely because of the size of the db with one
master table. Yes, maybe a vpn or some other network system would
allow it to be on a server some where, but the nature of our work means
we are always on the go and sometimes in an area with no outside
connection. Which is why I wanted to have a switchboard that promted
for a project to change the record source, so that they may send me the
table for that particular project and I inport it and then set the
record source, and then export it. They would have to delete and store
the projects on a disk when they are done to save space. Once the
projects are finished they will rarely have to go back to them , so I
would keep a master copy.
The other issue is that these records are entries of legal documents,
so the fields are required to be quite large, right now I have them set
to memo because of the length of the text is greater than allowed under
the text setting, I know this makes is work slower.
I would really really, appreciate any help that I can get, I am open to
any ideas to make this easier on the users and me the maker
Thanks JoeD
