D
Drew
Why not just store the tblFiles ID values for both
records? I am assuming that your tblFiles has the
following fields:
Files_ID (hopefully autonumber for unique value)
FileLong
FileShort
.....
.....
If this is the case, you should be storing the Files_ID
value in your tblLibrary. Using a relational table
structure is far faster and simpler. Storing data in
a "flat" structure is usually unneccessary. Now changes
in the tblFiles will be automatically "update" the
tblLibrary table.
If you wish to still use this flat approach, you may use
combo boxes that have the rowsource set to the tblFiles
and have each pull both values from the table. Only show
the value you wish for each box by using the column
widths to show the value (1";0") to only show the first
record. Bind on of the two boxes to the value of the
other box so that they mutually update each other. Use a
code such as me.filelong = me.fileshort.column(1) ((These
are zero based) in the After Update Event.
Hope this helped.
Drew
records? I am assuming that your tblFiles has the
following fields:
Files_ID (hopefully autonumber for unique value)
FileLong
FileShort
.....
.....
If this is the case, you should be storing the Files_ID
value in your tblLibrary. Using a relational table
structure is far faster and simpler. Storing data in
a "flat" structure is usually unneccessary. Now changes
in the tblFiles will be automatically "update" the
tblLibrary table.
If you wish to still use this flat approach, you may use
combo boxes that have the rowsource set to the tblFiles
and have each pull both values from the table. Only show
the value you wish for each box by using the column
widths to show the value (1";0") to only show the first
record. Bind on of the two boxes to the value of the
other box so that they mutually update each other. Use a
code such as me.filelong = me.fileshort.column(1) ((These
are zero based) in the After Update Event.
Hope this helped.
Drew