Search results for query: *

Hi, There is yet another aproach than mensioned. It's not allways possible to use, but it's extremly flexible and .. quite demanding for the fe developer. Use 4 tables my_products : common data storage for id etc. prod_id etc... my_category cat_id cat_name my_fields : fields...

Hi irishjoe, and the rest of you I don't beleive you have much choice, but to go for one of the .dll, .ocx sulotions if youre running Access2000. Have a look earlier in this thread (the posting by krymat) that one didn't work for me, but I haven't tried the sulotion you can find in...

Hi Stephen and the rest of you reading this. I beleive you are using the design from the FAQ. And I'm sorry I haven't updated it yet. Have a look at my postings [Jul 6, 2004 -the one with a download link] and [Jul 17, 2004]in this thread, and all your problems are solved :) Jollygood [pipe]

Thanks for your deebugging work directorz. The error code you get is not a "real" error. This sulotion is only working because I'm taking advatage of Access built in error handling to cancel the "go to next record" command caused by scrolling the wheel. In the code you downloaded I just assumed...

directorz The error is exactly what it says. You have declared a procedure more than once wich is forbidden. I sugest that you step through your form code and remove one of the procedures that ,in this case, looks like this: Private Sub Form_Error(DataErr As Integer, Response As Integer) .. etc...

I've put a temporarry link for you where you can download an example database. Follow this link: http://www.brynte.se/tmpaccdl/TurnOffMouseWheelExample.zip It will be removed in a couple of days. jollygood

I'm sorry to hear directorz. I've implemented it in an app that I'm developping and it works great. I've even managed to make Access not displaying the info message. To the user it looks like the form is just ignoring the mouse wheel for the main form, but they can still use it in a sub...

I have now come up with another way of solving this problem and it can be read att: faq702-5263. Thanks directors for inspiring me to look in to this mater once again and forcing me to come up with a more graceful solution than before. (I hope it is ;-) ) jollygood

Hmm.. I assume you have made sure there are no missing refferences. When you get an error report like this. The missing sub/function name you see is almost allways not the one youre looking for. Access does a check on the whole module when loaded and the error is reporting the first function...

Hi this is a tricky one. The only solution I can come up with so far is to: Set a filter on the form which is released in code when a "Next record" buton is pressed. Put this in your button klick event Me.Painting = False 'Stop the screen from flickering Me.FilterOn = False 'Release filter and...