Search results

Yes exactly. So we mark it [UNSOLVED] from the start. Something that's there is more noticeable than something that isn't, so people would then be more likely to do something about it.

We all feel like that sometimes. I am a little confused as to how it works on the other form but not this one. That other form's record source must include the field being filtered or there would be an error. It's worth having another careful look there, before smashing the computer. If you...

I notice from your combo box query image that tblBemusterungsstelle doesn't include the field indBemusterungsstelle.

No doubt this has been written about before but I'm fairly new and too lazy to search through thousands of posts (search for "Solved"? Well I just tried!) Solved posts are rarely marked as such. So people who want to help can assume the post has been solved when it hasn't, or waste their time...

Simplest code to requery a combo box is me.[ComboBox].requery Replace [ComboBox] with the name of your combo box (no quote marks).

I think Access is telling you that indBemusterungsstelle isn't in the form query results. In your image, there is no indBemusterungsstelle in the fields at the bottom of the screen. Try adding this field and see if it works then. (Boy you don't half have long words in German!)

Can I recommend using the query design facility in access. That way you can switch between design view (which is a really clear way of seeing what you are doing) and SQL view (which gives you the code with all the correct commas and semicolons!) One day I may learn SQL code properly, but...

Great rule Doc Man, but try telling that to my kids! (and grandkids!) In fact I am still learning it myself!

Possibly the reverse is happening. I see you have included apostrophes around the value of an ID field. If this is numeric, the apostrophes may cause an error. So if StateID and LicID are numeric then this code: WHERE [StateID]='" & Me.State.Value & "' AND [LicID]='" & Me.Lic.Value & "'")...

Hi Shafara, Just a thought - did you remember the semicolon ";" at the end of the sql code? The source sql code for the combobox would be different from that of the form itself because the combobox has a particular function within the form. I can't say more than that because I don't have...

Sounds like you're doing what I would do. I assumed you tested running the query from the query designer. If it runs, the sql should be right, except for criteria expressions that look up from forms etc (e.g. "xyz = '" & string & "'").

Minty is right. Mine would work. His would go faster.

And when you added the extra bit, did you first add this in Query Design View and then read off the sql?

Hi Shafara, I'm no good in sql either, but what works is to test it in a query design, then modify the query, switch to sql view and copy the resulting sql. You can clearly see what is going on in query design and the query builder translates it all into sql for you.

Yes it is possible. On your "old form" have a Combobox containing the dropdown list of the old records (bound to the ID fields of those records). in the AfterUpdate event for the combobox, you open the new form: DoCmd.OpenForm "[new form name]", , , , acFormAdd Then you populate the fields...

Just a small point. You say "I don't think its a missing reference". I suggest you check the references in both accdb files. Not just that they are ticked ('checked' in US speak) but that they are in the same order (I only recently discovered that makes a difference!)

MrHans is right about the space after "Where". Also I see no semicolon ";" at the end of the SQL. I also see no point in "...rec_Type = 'P" & "'" why not "...rec_Type = 'P'" There may be other errors in the SQL. But more to the point, your sub doesn't actually update anything - it just runs a...

Microsoft has described exactly your scenario, but when Word (not Access) is the application being controlled by automation. i.e. it works the first time but the second time produces error 462. The scenario they describe is where: "Visual Basic has established a reference to Word due to a line...

If you really must show something on your form other than a tick in a box, you could 1. In your main table, change the yes/no field type to Byte. 2. On your form put a combo or list box with a VALUE LIST of 2 columns, with a row source such as: 0;"Not as Such";1;"Yes Definitely"...

Dick has not said which field is being updated to "(New)" or "Open". It is probably not the ID field itself but a different field (possibly called "Status") that tests if the ID field is null and displays this value. That would suggest to me that the "ID" field is only populated when the record...