Disappearing Data

[jaad]

How can I help my the data from a combo box from disappearing when I change record?

the data is coming from a query that is made to limit the value list of a combo box depending on the value of the first combo box. I used to have the name before and it worked great but decided to changed my system to bound the ID instead for greater accuracy.

[NeoPa]

Can you clarify your question Jaad. I'm afraid I cannot understand what you're trying to describe.

[jaad]

My Apologies,

I used to have 4 combo boxes where the first combo was looking up [categories]. The second combo was looking up [types] in a query limited by the value of categories. the third [product] was taking values from another query limited by the value of [types] and finally [supplier] was taking value from another query limited by [product]

all of those values were the "names" not the ID. and it worked fine.

I recently changed a lot of thing in the database and decided to use the ID instead of the names but now when I try to do the same thing that I used to do in my subform (witting down a purchase order items) now every time I change line or maybe I should say record, the value that was showing above disappears.

I am aware that the ID field is bound to the combo and hidden and reason why nothing is showing when I move.

I have tried a hundred different ways from advices from different sites but none worked so far.

Another thing that never seem to work is the "combo box. requery" I always have to do it manually no matter how or where I write it down.

Right now I only have [category] [product] and [supplier]
I had to return using the "names" of the [product] and [suppliers] instead of [id] like I wanted to do because the data disapears. dam I suck at this

[NeoPa]

This is hard to follow without the database I'm afraid, and harder to determine what the problem is even though I have a slightly clearer understanding of it now. Unfortunately, you're sort of asking what's wrong with your new design without including any details of it. I suggest you try attaching the database for us to have a check over.

When attaching your work please follow the following steps first :

1. Remove anything not relevant to the problem. This is not necessary in all circumstances but some databases can be very bulky and some things do not effect the actual problem at all.
2. Likewise, not entirely necessary in all cases, but consider saving your database in a version not later than 2003 as many of our experts don't use Access 2007. Largely they don't want to, but some also don't have access to it. Personally I will wait until I'm forced to before using it.
3. If the process depends on any linked tables then make local copies in your database to replace the linked tables.
4. If you've done anything in steps 1 to 3 then make sure that the problem you're experiencing is still evident in the updated version.
5. Compile the database (From the Visual Basic Editor select Debug / Compile {Project Name}).
6. Compact the database.
7. Compress the database into a ZIP file.
8. When posting, scroll down the page and select Manage Attachments (Pressing on that leads you to a page where you can add or remove your attachments. It also lists the maximum file sizes for each of the allowed file types.) and add this new ZIP file.

It's also a good idea to include some instructions that enable us to find the issue you'd like help with. Maybe some instructions of what to select, click on, enter etc that ensures we'll see what you see and have the same problems.