Want to populate a form with data from a table, the Id number is keyed into the form and once it's matches with the Id in the table I want the other fields on the form to be populated with the data from the table.

In general you initiate this process by pressing the "Relationships" button on the MS Access toolbar. It is the button with three small boxes arranged in a triangle shape.


When it first comes up it will give you the option to add tables. You can add any set of tables including the possibility of adding one table more than once (you would do this if you wanted to create a relationship between fields in the same table).

Once you see the tables you're interested in, you simply drag the field from one table over a field in another table. The fields should be those that will define the relationship. Once done, you should see an Edit Relationships window. You can get back to the Edit Relationships window later by double clicking the line in the relationships window.


MS Access does a good job of figuring out the relationship type. For example, if you match a field in one table, that is not a key, with a primary key in another table, Access will make this a Many-to-One relationship.

This can become a very deep subject. Hope this at least gets you in the right direction.

You need two things:
1. JSP/Servlet knowledge.
2. SQL Programming basics

1. Create your PR jsp page which contain a form with method post and action to a servlet that will handle the insertion of the data to a database table i would add winners table containing ID, Frkey, thenumber

2. A servlet that will generate the number and cross check with those who guessed right and update the winners table with that data.

3. A servlet that will do an inner join with the pr and winners tables to display the results.

Good luck

Press [2nd][+] (MEM)
Select [4:ClrAllLists]
Press [ENTER]

Now you are ready to create a table from the expression of a function.

Press [Y=] to open the function editor.
On line Y1= enter the expression of the function
Press [2nd][GRAPH] (TABLE) to create your table
You will see two lists X, and Y1.

If your table is not generated from the expression of a function, but from raw experimental data, you use the [STAT][1:Edit] key sequence to open the Lists L1 to L6 and populate the two you want.

Change the "Data entry" Property to "No". This is what preventing you in viewing other records.

Relationships

After you've set up multiple tables in your Microsoft Access database, you need a way of telling Access how to bring that information back together again. The first step in this process is to define relationships between your tables. After you've done that, you can create queries, forms, and reports to display information from several tables at once.

A relationship works by matching data in key fields - usually a field with the same name in both tables. In most cases, these matching fields are the primary key from one table, which provides a unique identifier for each record, and a foreign key in the other table. For example, teachers can be associated with the students they're responsible for by creating a relationship between the teacher's table and the student's table using the TeacherID fields.

Having met the criteria above, follow these steps for creating relationships between tables.

1. In the database window view, at the top, click on Tools ---> Relationships
2. Select the Tables you want to link together, by clicking on them and selecting the Add Button
3. Drag the primary key of the Parent table (Teacher in this case), and drop it into the same field in the Child table (Student in this case.)
   
4. Select Enforce Referential Integrity
   
   • When the Cascade Update Related Fields check box is set, changing a primary key value in the primary table automatically updates the matching value in all related records.
   • When the Cascade Delete Related Records check box is set, deleting a record in the primary table deletes any related records in the related table
5. Click Create and Save the Relationship

You need to create 2 tables. Create one table with just the Center Number, County and Center fields, using the Center Number as the primary key, lets call this table Center. Then create the other table with all the other fields you need, lets just call it the Main table for now.
Then create a relationship between the Center table and the Main table using the Center Number for the relationship. The relationship should be a One-to-Many from the Main to teh Center table. When creating the form, you take the fields from both tables. When you input the Center Number, the County and Center should be automatically filled in.

this discussion could go on for days (month? a semester at least?) but data is any piece of information you want to capture and save. a name. an address. a phone number. (actually they are examples of pieces of data - and whether you capture and save them or not they are still pieces of data). data "forms" a database when you save it (in the dataabase).

the database usually has tables representing related pieces of infomation.

Example:
the CLIENT table may have the following fields:
Client Number
Client Name
Address
Phone
Contact name
etc., etc.

the ACCOUNTS_RECEIVABLE table may have
Client Number
Invoice Number
Invoice Date
Invoice amount
etc., etc.

Notice how the CLIENTS table is "related" to the ACCOUNTS_RECEIVABLE table by the Client Number - hence the term you may have heard RELATIONAL database.

any more in depth please ask.

Firstly you need to determine/state whether you are using a database application, such as Access, MtSQL or MS SQL and programming them to do create this application, or are you using a programming development tool such as Visual Studio, ASP.NET, PHP or the like, as the solution and guidance will be different for each.
In terms of the data design, you should store the data necessary to identify each employee uniquely and each data point per employee needed to calculate their payroll. You should then store the generic (applys to all employees) such as tax rates, in separate tables and call on it to calculate wages and other paystub data.
For instance, the employee first and last names and tax ID should be a sufficient unique identifier. Create a table for just employees, their names, tax ID, start date, schedule, pay rate, number of deductions, direct bank payment data, etc., and whatever else you decide you need for each employee. You can calculate their wages by multiplying their rate by their schedule and applying the appropriate tax rate and medical/witholding deductions as you go, so calculated data does not need to be stored and consume database space. 
You'll likely need a separate table for common data such as tax rates, one for deductions/witholdings, one for holidays, one for vacation accrual rates, one for medical rates, etc. This data if common to employees does not need to be stored per individual, as that would cause redundant replication of data. If the employees are on an hourly rate, rather than a set salary/wage, then you'll need a table of worked hours per employee, akin to their timesheet data. If you use a timesheet/timecard, the entering and storing only the totals and keeping the physical timesheet for backup records should suffice.
Once you design and populate your database as suggested above, then it's a relatively-simple task of calculating the computed paystub data and storing the salient resulting datapoints for the record.
Consider a reporting application, such as Crystal Reports, for your printing needs, as its far easier to configure Crystal or similar product to format reports, paystubs, checks, etc., than coding these from scratch.
Hope this helps.

Hi vrusha,

Your right hlookup is very simular to vlookup, the key difference is it searches along the top row of the table, finds the matching data and gives you one of the below cells (depending on how you write the formula), just think of a vlookup on it's side.

The formula works like this:
=HLOOKUP(lookup value, table, row_index_number, range_lookup)

lookup value = is the value you want to match against the table i.e. ABBA

table = the range of cells that make up the table you want to search i.e. A1:D300

row_index_number = the number of rows from the top of the table you want to get the value from, 1 is the top of the table, 2 is directly below

range_lookup = if you want an exact match type FALSE, if you want the nearest match type TRUE

It sounds like you are using an ADO data set, which is probably one of the more difficult, especially for a beginner. What you are seeing is that the data does not update related controls until the data has been committed to the row you are updating. Set the Binding.DataSourceUpdateMode to DataSourceUpdateMode.OnPropertyChanged.

Or, depending on the version of Access you are using, the option may be somewhat different. The point is to tell the control to update "on change" - so that once your data is in there (a change) the other items you want to happen will occur, as the row has been committed (recorded). Thanks for rating FixYa!