Recent content by MajP

My point is that there are many queries that you can use to return the duplicates. Most of these require a subquery or aggregate query which makes the whole query not updateable and thus make your form not updateable. Therefore, if you need your form updateable, use the first technique with a...

If you notice the one using the Dcount is editable. The second uses an aggregate query which makes it non updateable. If you need to update the form then the dcount is the easiest.

See if this example helps. One uses the Dcount. The other query uses an aggregate query to get the counts.

OK. Then I would look at some version of what @DHookom suggests. You can then format where count is > 1.

This is confusing. When we say duplicates we mean having the same value repeated in the same field. But your example could be that or you could mean having the same value in two different fields. You show both. If you mean two different fields then you can create a new calculated column...

That is what I assumed and makes more sense, but it sounded as if you could import objects which would be a very different situation.

That is good, you are much better off that the DB is split. But still unclear if you can import some "objects" (forms, reports, queries). In rare cases it is a single form or code that is corrupting the db. If you can import objects one by one then you can slowly recover until you determine...

Also I would hope that any DB at that size does not actually have the tables and objects in a single db? You have to have that db split and unfortunately you will probably need more than one backend. With multiple backends you cannot enforce referential integrity across the multiple backends...

Are you saying you can import the tables and objects from the corrupt db? Usually if it is corrupt you cannot get to those so you may have chance. If so can you import a few tables at a time and open them? Can you import a few forms/report and open them? For sure if you can import tables, I...

If you say so.

As I said, this is as expected behavior and it has nothing to do with if the subform has focus or not set by the calling code. We all should have caught it earlier. You cannot hit return in a textbox and expect to stay in that textbox unless you change the EnterKeyBehavior property of the...

Although this was questioned by @BlueSpruce as being overkill. It is doing exactly what I said was happening. The focus is being set properly to txtProductCode and then immeidately after that it moves away to the next item in the tab order. This is probably normal behavior due to order of...

Thats the whole point. You seem unwilling to read the OP's post, or I do not know where you are coming up with this. There is no event being called from the subform. No such thing exist regardless of any placeholder name (I get that). Private Sub YourSubformControl_AfterUpdate() Clearly the...

Does not makes any sense. We must be reading two different posts. You need to look at what the OP posted. There is no "YouSubFormControl" involved. His barcode reader is updating the main form txtProductCode which is then updating the subform. What makes you believe that this is being called...

My next guess is that the focus is first set and then something causes the focus to move away. Such as a pending event or pending code. To test Me.txtProductCode = Null DoEvents Me.txtProductCode.SetFocus Msgbox "Check to see if focus is set" One thing that can cause the main form to...