Speed up inputs 1

[mxp346]

I have a form that when the user fills it out with an ID, Description, Category and Occurance Number, the inputs are stored in an Occurance table. There is another table that has the ID's listed and has the associated Description and Category. So that the user doesn't have to input the Description and Category every time, I wanted those values to be looked up based on the ID typed in and then placed in text boxes on the form . How do I go about doing this? What properties do I need to change?

 

[dawnd3]

Do you have these tables linked in the relationships window?

Dawn

http://www.calliopeconsulting.net

 

[rajeessh]

During the ID field After Update
Open The RecordSet Fetch the values
and place them in the respective text boxes

 

[mxp346]

I don't have the tables linked because I was just using the one table to lookup the other values after the person enters the ID.

 

[rajeessh]

Just open the connection to the required DB
Use the connection And open recordset and try in that way

 

[WildHare]

Check out the DLOOKUP action - it does exactly what you want.

txtDescription = Dlookup("Description", "OtherTable", "OtherTableID = '" & Forms!YourForm!YourInputID & "'&quot

(Assuming YourInputID is a text guy - the single quotes are needed. If not,

Dlookup("Description", "OtherTable", "OtherTableID = " & forms!YourForm!YourInputID )


Jim How many of you believe in telekinesis? Raise my hand...
Another free Access forum:

http://www.forumco.com/jmhare

More Access stuff at

http://www.jmhare.com/wildhare2.htm

 

[mxp346]

The Dlookup function worked well. Now I got the form working. I made an add record button to save the information to tblOccurance. When I click it, nothing is added to the database. Do I need to write a macro and place it in the On Click Property of the button? If so what is the action property that should be used?

 

[mxp346]

I finally figured it out. Thank you for all your help.

 

[mxp346]

Actually it's still not working :/ It doesn't save the values that were looked up to the table. So I have the control source as =DLookup... It looks up the values right but when I click the fields that have DLookup in them don't save to the database, only the values that the person enters.

 

[WildHare]

You really don't need to save the values again - if they are in a lookup table, just use them when ever you need them, either via a join query, or with the DLOOKUP function.

It's considered bad form to store a value in two separate places (except for joining keys, obviously)

Jim How many of you believe in telekinesis? Raise my hand...
Another free Access forum:

http://www.forumco.com/jmhare

More Access stuff at

http://www.jmhare.com/wildhare2.htm