storing two bits of info at once

[Muzicmn969]

I posted this question last week but dont think i was thorough enough. gonna try it again

what i have is a db with a few tables....one is a airspaceid, it gives the airspace name, and default altitudes among other stuff.....one of my other dbs is an event db...it tracks when the airspace is used what times and what altitudes. now the altitudes defined in db1 are basic default altitudes which do change from time to time.

on one of my forms i have a combobox which looks up the airspaceid from db1 and stores it in the events db. this db also has a textbox which is bounded to the airspaceid combo box, it displays the default altitudes that coorespond to the appropriate airspaceid. Now the tricky part... sometimes the altitudes that the airspace goes active to change from the default. I can change the alt in the form but it isnt stored in db2 only because there is no field and i dont know how to make access store a second field based on the original combobox. I need the report to display the default alt if it hasnt been changed or the new updated altitudes if they were changed. i also need to make sure that when the altitude is changed that the table with the default altitude is NOT changed. This way the default alt is there for the next use.

any ideas would be greatly appreciated

Ricky

 

[Jack Cowley]

If you link the table (from db1) that is the Row Source for the Combo box then you can add data to that table. I am not quite sure what you want to do since this data can change so are you sure you want to store the data? If the change is only applicable to the moment then a global variable may be adequate for what you want to do.

hth,
Jack

 

[Muzicmn969]

the reason for the stored default altitudes is for ease of use. The defaults are used regularly but on occasion need to be changed. do you recommend that i create a second field???

i guess what i am trying to accomplish is to store the default alts in another db while having the ability to change them before they are stored


thanks again

 

[Jack Cowley]

I am not quite sure of the reason for a separate database, but be that as it may I would use the table as a 'lookup' and store the value selected or entered in another table. You might want to condsider using the Not In List event of the combo box so that you can add new values to that table. I do not know how your database works so I am having to guess at possible solutions and using Not In List may be a very good one....

hth,
Jack