Search results

As far as I can tell, yes. What next?

They're not linked, but I want them to be. While I was entering the data from each hand-written log sheet into the table, I wrote the ID number -- assigned by Autonumber -- onto the sheet. When the record got deleted somehow -- probably when I was trying to make corrections -- the number on...

I was using an autonumbered ID field to link the table to others. Some of my records have been deleted for one reason or another; so the ID numbers go from 7 directly to 13. Is there any way of adding a new record that reuses the ID of one of the deleted records? It would sure be easier than...

I'm not mixing them up. I need to do both. Originally I just entered data in the table. Recently I created the form and subform as a better way of accessing the data. The form is a "log" for each employee; the records in the subform are the individual log entries. It works fine for adding new...

My subform draws from a query which in turn draws from three tables. Its easy enough to add a new record in the subform, but what about when I need to add an existing record to the form? I can't enter the record number in the ID column because it's an autonumber field.

I was looking for a way to do that and definitively associating a PaychecksTable record with a LogsTable record. Maybe it's not possible. However, I did think of a workaround. I made a query that combined the two tables -- joined by a "PaychecksID" in each table -- and used the query, instead...

Okay, that is helpful. However, as you know, the underlying table of the form is LogsTable, and the Wizard only gives me the choice of fields from that table. How do I add fields from PaychecksTable to the form? And how do I add a ComboBox to select a record from PaychecksTable?

LogsTable is accessed through a form. I need to add a combo box that lets me select a record from PaychecksTable, so I can assign a paycheck to that LogsTable record. I also want to see the fields from PaychecksTable on the form too. This should be easy. Part of my problem is the Combo Wizard...

Yes that's exactly right. Someone else on this board told me I could do this, but I thought I'd be left with the "related data", not the IDs. No one explained what the next step would be. Eventually I figured out a way to convert the related data to the IDs, but you just showed me the easy way...

I'll take the time to read it. But one thing bothers me: Everything I've read so far about normalizing a table assumes that -- in my case -- the "Client" field is just a list of client names. In my case, it's not -- its a lookup to a Clients table. If I follow the usual instructions, I think...

Okay, I tried it and sucessfully converted the Checks field to a standard field. Now, how do I "look up" this value in the Checks combo box on the form? Please, I'm not THAT newbie. ;)

I have a table, "Sessions", that has lookup fields which each pull in a value from the Employee, Checks, and Client tables. (They're each "one" to the Session table's "many". ) Because I'm moving to forms, I want to remove these fields - or at least, not use them any more. When I get the form...

Okay. Umm...could you walk me through the steps, using my example? Again, I have the Sessions table, the Clients table, and I need to match every Client to one or more Sessions. Thanks.

This is what I mean: http://www.mvps.org/access/lookupfields.htm He seems to make some good points.

Here's what I have so far: The form contains a subform, which draws records from the a form called "Sessions Subform". As you probably know, this form is a datasheet form (a form that looks like a table, which I think is cool), that draws its records from a table called "Sessions". The...