Possibility of Form

[Joan]

I've created my database with "normalized" tables. I have
a form, that employees use to enter system information for
each customer. Some customers have more than one system.
When a system is added it needs to be added to the
appropriate report so that it gets scheduled for service.
I've got a report that pulls up the information according
to Customer ID, Service, Type of System and Week. There's
room for 20 systems to be listed on the report. Right
now, each system is put on its own report. I need to have
all systems that are identical in the following categories
to be listed on one report: Customer ID, Employee, Week
of Service, Service Type and System Type. I need an
example of code or an idea of how to program my form so it
automatically adds the information to the next available
textbox once the first textbox is filled.

I would greatly appreciate any advice that can be given or
examples of code. Thanks for any or all advice that is
given!!

 

[Albert D. Kallal]

I've created my database with "normalized" tables.

I will have to assume you know what is meant by normalized tables.

There's
room for 20 systems to be listed on the report.

Gee, I don't understand what the above means. With a normalized database,
you should not care if you have 5 systems, or 500. The whole idea of a
normalized data designs is that you don't have to change things like reports
or data entry screens. A normalized data system means you have freedom to
have only 2 systems, or go ahead and add 200 systems to one customer. If
your design is truly normalized, then I don't know what you mean by 20
systems limit here?

I need an
example of code or an idea of how to program my form so it
automatically adds the information to the next available
textbox once the first textbox is filled.

Again, what do you mean by next available text box? Does not a continues
form (or sub-form in your case) do that now? Again, perhaps we are having
difficulties with different term, but again the above request does not fit,
or sound correct when talking about a normalized table design. I would
assume during data entry that you have some type of sub-form that allows you
to enter 1 or 10, or 34 systems that belongs to one customer. Is this not
what you have now?

If your data design is normalized, then I don't see why you can't sort, and
use the sorting and grouping features of the report to group customers and
their systems together. In addition, likely the report could use
sub-reports, and that one sub-report in the details section of the report
could display all service records for each customer. If there is only room
for 20 systems, then I would assume the page would simply continue on to the
next page for the report? Regardless, any kind of speak that says you have a
limit during data entry does NOT sound normalized at all.

Not knowing any of your table designs, my bets on are on using a sub-report.
Often, you can get the same results with sql joins, and "grouping" or hiding
the repeating data that results from sql joins on your report. However, a
sub-report is usually much easer, and certainly much more intuitive from a
relational data point of view.

Good luck..and feel free to expand on what you mean by that "20" limit..

 

[Henry Smith]

You have a common problem of database design and implementation. There are
a multitude of answers to your question. The multitude of answers available
is primarily because you haven't described your problem in sufficient
detail. However, I recommend a resource to help you solve your problem
today and problems of tomorrow in addition to this forum. I strongly
suggest you invest (low dollar cost) in a set of books named "Access 2000
Developer's Handbook" (a two volume set), author Ken Getz, publisher SYBEX.
This set of books is available on line from Amazon.com and several other
sources for a discount. A very good set of tutorials, with a CD of all the
examples, easy to read and a great reference.

Wish you success and hope to see you here again.
Cheers,
Henry