Data Entry Page

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a form that will be used for data entry.

This is split in two sections:

The top half identifies the client through a number of cascading combo
boxes. This client then is shown in a subform, to see if the data in the
database is correct.

The bottom half is for data entry relating to the client eg Items, period etc.

I want all the information on the page to be exported into a table and
stored so that queries and reports can be extracted. The problem is when I
turn on the data entry function in properties the cascading combo boxes stop
working. How do I export the data on the sheet into a table without losing
the use of the combo boxes and subform?
 
Aren't there already tables behind your form? I'm not understanding the
context of your question.

Thanks;

Amy
 
I have tables that make up the combo boxes eg

Country
Name
Address

This information is then displayed in a subform.

I then have text boxes that I wish to add data into

Destination
Items
Period

I want to click a button and all the information that appears on the form be
exported into a master data table.
 
For what purpose? I'm missing why you want to do this. What about just
using queries to combine the information that's been entered into the form?

-Amy
 
I want to reference the data back to each client, I tried with a query and
the problem i had was for 2 clients with the same name the data duplicated.
eg Ford may have about 10 different accounts. I need the data entry to be
matched to the exact account. The top part of my form and subform pull out
the client details. Would I be able to use a second subform for the data
entry side. If each account in the top section had a unique identifier and
this was entered into the subform and then exported then i would be able to
link the client to their shipments.
 
It sounds like you need more tables

Company
=======
CompanyID
CompanyName
....more identification for the company as a whole if needed

CompanyDivision
============
DivisionID
CompanyID (Tells you what company the division is part of)
DivisionName
DivisionAdd1
DivisionAdd2
DivisionCity
DivisionState
DivisionZip

Then you need, on the order side

Orders--is just a way of creating an order entity to associate a division
and the items it ordered
=====
OrderID
DivisionID (You know the address etc, from the division table)

Items
====
ItemID
ItemDesc
ItemPrice
ItemEtc

OrderItems
========
OrderID
ItemID

Now, you should find it relatively easy to create a cascading form design to
enter this info, and if you define the relationships you should just be able
to show the tables in the QBE and select the fields you want.

Basically, you want to manufacture data and put it into spots that don't
exist. Make the spots first, then the rest follows.

HTH;

Amy
 
I've just answered my own question!

Tried it and it appears to work, only problem i've got now is that instead
of adding data it appears to be overwriting the last entered data. Just a
small thing now for me to think about
 
Back
Top