VB Code won't run after Windows Update

[Shepenwepet]

I have a complex database that has modules and forms in the front and links to a separate back end. People in our office run Access 2000, 2002 and 2003, all on XP. We have never had this issue before in six months of development.

The front end was primarily developed in Access 2000, 2002 and Visual Basic.

As of this morning, those users running the Front End in Access 2003/XP have been unable to open the database, call the separate modules, or to use any forms that are related to those modules. Open the front end, and you get "Invalid Procedure Call or Argument" before any form or other feature will open. We ran the Debug program in the VB screen and it tagged "Private Function" or "Private Sub" before every segment of the separate modules.

Earlier versions of Access have no problems.

The culprit here appears to be the updates downloaded on these computers this past Friday. Those updates are (Office Updates) KB919029, KB921587, (Windows Updates) KB923980, KB924270, KB890830, and KB922760. I think it must be one of the security updates that suddenly decided that older VB code must be spyware.

I am not fluent in Visual Basic, and would appreciate some guidance on how to find the cause of this problem. Needless to say, there is a level of urgency here.


S.

 

[llkhoutx]

Invalid Procedure Call or Argument

indicates that Access is calling a procedure (subroutine or function) which it cannot find or that not enugh argument are provided in a call. This error also fires when program References are not set correctly.

Use the debugger to identify the instruction cauting the probem.

 

[Shepenwepet]

llkhoutx:

The first code that trips:

Public Function ListFiles(strPath As String, Optional strFileSpec As String, _
Optional bIncludeSubfolders As Boolean, Optional lst As ListBox).

Commenting this code out causes it to trip on the next procedure, and so on, regardless of the content. All of these procedures ran flawlessly 72 hours ago.

UPDATE: The error changed after one of the security updates was removed. It now displays the "Visual Basic is Corrupt" message on loading the front end. The helpfile suggests that the database was incorrectly upgraded from 97, except the front end was developed in 2000 and 2002.

- Have compacted/repaired
- All references are intact

I understand from other posts on this forum that the "VB is Corrupt" message is the kiss of death, but the front and back ends still run flawlessly on every other computer, so the usual fixes don't seem to apply.

What is different about AccessVB 2003 that could cause this problem? Unfortunately, downgrading Access versions isn't an option here or I'd just dump 2003 completely.

 

[gemma-the-husky]

funny if its always been working - doesn't the compiler take you or your users to the error

it might be something silly like the order of ADO and DAO being the wrong way round in the tools references - i would check the references first

 

[Bat17]

Also check what level your macro security is set to. Do you get warnings about unsafe expresions when the DB opens?

Peter