Search results

Update 2: After substituting the offending code - at least what I thought it to be - from all subforms on the main form, the app now constantly asks for the main form to be saved whenever I change code in other, unrelated forms. It seems there is a deeper problem. I checked the System Objects...

Pat, thank you for drawing my attention to the validation problem, I will check that part. And sorry for the Spanish, I have the bad habit to use whatever comes to mind first - a wonder there is no German as well :) As to the primary problem, please see my update - there seems to be a deeper...

Update: I erased all code from the offending form, decompiled and recompiled, problem gone. Inserted the same VBA saved in a text-file (Notepad), problem again. I then deleted the sorting modules (see posted file), problem gone. Which is strange, because I use the same approach for sorting in...

Here it is, a bit lenghty...

I have only one Main form open with the mentioned three subforms. One of the subforms wants to be saved when I make changes to a third form which has no reference to it or to the main form

Yes it does, even if I don't change anything on the main form or one of the other subforms. You might be right and I will have to recreate the form from scratch.

No structural changes are made to the form from anywhere. It is just open in its main form, sitting there. When I work on some pieces of code of other forms, the 'offending' form is not affected whatsoever. I might just do as little as deleting a line of code on another form, and, when saving...

Addendum: I forgot to mention that the offending form is a subform on the main for, which is always open. This main form has - in different tabs - three subforms, and only one causes the problem. And no, the problem is not limited to changes on the main form or one of the other subforms.

Thank you for the suggestion. Please see the addendum to my original question.

Will give it a try, but it will take some time. Thanks for the suggestion.

I have several forms with VBA. Whenever I make changes to VBA in one of them, a specific form asks to be saved, even though no changes have been made to its VBA. I tried compact and repair database and decompile, no success.

Dear gth, thanks for your reply, but as I mentioned before I found the error, and now the code is returning the right result. !FInicio is retrieved from an unbound field on another form and can never be Null nor zero, because in that case I could not open the current form. But it still puzzles...

I finally found the error, and as usual, the problem is to be found in front of the Display. I'm quite ashamed to admit... table 2 has no field 'Fecha'. Which still leaves the mystery why in some instances the second DSum returned a result diferent from 0. Thanks anyway for the good ideas, guess...

Yes, I did that, including opening the db with SHIFT held down, compact&repair etc. To no avail.

Thank you, Ben, for the quick reply. In fact, the size of the db shrunk to 80%, so there had to be a lot of junk in it. Unfortunately, it solved the problem only partially: The first time the sub is called, the error ocurs in any case (A or B), then, by changing the filter criteria and calling...

I ran into a strange behaviour in a rutine that deletes a line in a table and then generates two values based on DSums. The second DSum allways returns '0'. Putting the Dsums before the delete, they work fine. The code: A) This gives the problem: CurrentDb.Execute "DELETE * FROM Table3...

I skipped 'GoTo' since I worked with the wonderful (structured) GFA-Basic for Atari, back in '87. In fact, I can only imagine one case (except for the mentioned case of error-trapping) of a useful GoTo, that is when a friend calls and says 'GO TO David's bar, I'll be there in 5 minutes'. All the...

This is a bit frustrating, as this site seems to be 'optimated' for the MS Internet Explorer, and I do not usually use that. Anyhow. Coming a long way from the dawns of home-programming (TI 55!), I ended up with Access (now 2007); having bumped my head ever so often into problems :banghead...