MS Access Filters VBA Debug Error

%3CLINGO-SUB%20id%3D%22lingo-sub-2163247%22%20slang%3D%22en-US%22%3EMS%20Access%20Filters%20VBA%20Debug%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2163247%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20All%2C%20we%20are%20running%20an%20Access%20DB%20that%20includes%20filters%20to%20help%20sort%20through%20the%20data.%26nbsp%3B%20Because%20of%20tech-refresh%20limitations%20we%20have%20two%20different%20type%20of%20workstations.%26nbsp%3B%20The%20filters%20work%20fine%20on%20the%20older%20workstations%20but%20users%20get%20a%20VBA%20debug%20error%20on%20the%20newest%20workstations.%26nbsp%3B%20Both%20workstations%20are%20running%20the%20same%20version%20of%20Office%20with%20the%20same%20features%20enabled.%26nbsp%3B%20All%20MS%20Access%20options%2C%20code%2C%20etc.%20is%20the%20same%20on%20both%20workstations%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20what%20could%20be%20causing%20this%20error%3F%26nbsp%3B%20Thank%20you%20in%20advance%20for%20any%20insight%20you%20may%20provide.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E~Marilynn%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2163247%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2163933%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Access%20Filters%20VBA%20Debug%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2163933%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977684%22%20target%3D%22_blank%22%3E%40MMLevinton%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20first%20thing%20that%20comes%20to%20mind%20is%20bitness.%20When%20you%20say%20that%20the%20version%20of%20Office%20is%20the%20same%20on%20both%2C%20I%20assume%20you%20refer%20to%20something%20like%20Office%202019.%20However%2C%20if%20the%20newer%20workstations%20were%20recently%20set%20up%2C%20it%20is%20possible%20that%20they%20were%20set%20up%20with%20the%2064%20bit%20version%20as%20opposed%20to%20the%2032%20bit%20version.%20One%20reason%20that%20could%20happen%20is%20that%20MS%20changed%20the%20default%20to%2064%20bit%2C%20so%20people%20would%20get%20that%20bitness%20without%20realizing%20it.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22bitness.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F257585iA02131A040919EA2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22bitness.png%22%20alt%3D%22bitness.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20help%20focus%20better%20on%20possible%20reasons%20for%20the%20problem%20and%20approaches%20to%20solving%20it%2C%20we%20should%20see%20the%20actual%20error%20message.%20Can%20you%20get%20a%20screen%20shot%20and%20post%20it%20here%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2165805%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Access%20Filters%20VBA%20Debug%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2165805%22%20slang%3D%22en-US%22%3E%3CP%3EGM%20George%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126074%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20response.%26nbsp%3B%20Please%20see%20attached%20screenshot%20document.%26nbsp%3B%20The%20code%20is%20exactly%20the%20same%20on%20both%20systems.%26nbsp%3B%3C%2FP%3E%3CP%3E64%20bit%20windows%2010%20OS%3C%2FP%3E%3CP%3EOffice%20Professional%20Plus%202016%3C%2FP%3E%3CP%3EThe%20differences%20are%20one%20workstation%20is%20a%20Lenovo%20ThinkPad%20running%20SDC%205.7%20(works)%20and%20the%20other%20is%20a%20Dell%20Precision%20running%20SDC%2010.1909.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20put%20in%20a%20ticket%20with%20the%20AF%20SDC%20support%20but%20am%20still%20waiting%20for%20their%20response.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello All, we are running an Access DB that includes filters to help sort through the data.  Because of tech-refresh limitations we have two different type of workstations.  The filters work fine on the older workstations but users get a VBA debug error on the newest workstations.  Both workstations are running the same version of Office with the same features enabled.  All MS Access options, code, etc. is the same on both workstations

 

Any ideas what could be causing this error?  Thank you in advance for any insight you may provide.

 

~Marilynn

7 Replies

@MMLevinton 

The first thing that comes to mind is bitness. When you say that the version of Office is the same on both, I assume you refer to something like Office 2019. However, if the newer workstations were recently set up, it is possible that they were set up with the 64 bit version as opposed to the 32 bit version. One reason that could happen is that MS changed the default to 64 bit, so people would get that bitness without realizing it.

bitness.png

 

To help focus better on possible reasons for the problem and approaches to solving it, we should see the actual error message. Can you get a screen shot and post it here?

Thanks.

 

GM George, @George Hepworth 

Thank you for your response.  Please see attached screenshot document.  The code is exactly the same on both systems. 

64 bit windows 10 OS

Office Professional Plus 2016

The differences are one workstation is a Lenovo ThinkPad running SDC 5.7 (works) and the other is a Dell Precision running SDC 10.1909.  

I have put in a ticket with the AF SDC support but am still waiting for their response.

@MMLevinton 

Did you also confirm that they are both the same Bitness, 32 or 64?

@MMLevinton 

That looks more like a missing reference.

 

Open the VBE and click on Tools-->References. Are any of them flagged as "Missing"?

References.jpg

 

Yours will, of course, have different references, depending on which ones your relational database application uses. We are interested in those that are "Missing" on the computers that error out, but which are okay on the other computers.

YES!  @George Hepworth 

That was exactly the issue.  I copied and pasted the missing *.dll file and ...poof... the filters worked.

Thank you George!

Congratulations on solving the problem.

Continued success with your project.
We are restricted by AF standards to use Office 32 bit.