Corrupted VBA

[paul.m.henderson]

Hi,

We have an application that uses a Access 2003 ADP (ADE in production)
as its front-end. Over the last 6 months or so we've seen an increase
in the amount of VBA corruption. Users receive odd error messages
like, "Can't find field """ or "Invalid expression """. We've tried
all the suggested steps, including, Compact & Repair, Decompile, Save
As Text => Import As Text, and Importing All Objects into a New ADP,
none of which have an effect. Another factor might be that we're
using source-code control with the ADP and doing a lot of importing
and exporting of the forms/report/modules. Does anyone have
experience with SCC causing corruption? Does anyone have any other
suggestions? I'd be happy to include the full text output of one of
the troublesome forms if that will help.

Thanks!

 

[Jim Burke in Novi]

I don't know anything about ADPs, but when I first tried importing Modules or
Reports/Forms that have accompanying code I had problems. I found that I had
to go into VBA, do a compile and then do a Save while still in the VBA code
right after doing the import, otherwise there was some sort of corruption.

 

[paul.m.henderson]

I don't know anything about ADPs, but when I first tried importing Modules or
Reports/Forms that have accompanying code I had problems. I found that I had
to go into VBA, do a compile and then do a Save while still in the VBA code
right after doing the import, otherwise there was some sort of corruption..

Ok thanks for the tip, I'll add that to the list!

 

[Klaus-Dieter Gundermann]

Hi,

We have an application that uses a Access 2003 ADP (ADE in production)
as its front-end. Over the last 6 months or so we've seen an increase
in the amount of VBA corruption. Users receive odd error messages
like, "Can't find field """ or "Invalid expression """. We've tried
all the suggested steps, including, Compact & Repair, Decompile, Save
As Text => Import As Text, and Importing All Objects into a New ADP,
none of which have an effect. Another factor might be that we're
using source-code control with the ADP and doing a lot of importing
and exporting of the forms/report/modules. Does anyone have
experience with SCC causing corruption? Does anyone have any other
suggestions? I'd be happy to include the full text output of one of
the troublesome forms if that will help.

Thanks!

Hi Paul,

did you ever resolved your problem ?
I'm asking because I'm struggling with a similar problem, but its an MDB
created with Access XP runing on Windows XP, but these errors also occur when
running the MDB in Office 2007. The errors I see include such weirdness as:
-----------------
Public Sub1()
sMyTable = "Customers"
sMyCondition "CustID = 1234"
sSQL = "SELECT Name FROM " & sMyTable & " WHERE " & sMyCondition
Debug.print sSQL
end Sub

Customers WHERE CustID = 1234

---------------
Public Sub2(Param1, Param2, Param3)
Debug.print Param1, Param2, Param3
end Sub

Call Sub2("One","Two","Three")

Two, Three

---------------

Nothing helped, no Decompile, Compact, Repair, no SaveAsTex, no Export to
another Database. The error will vanish after a Decompile but will return
randomly in another codepart after a short time.

PS: I am NOT using any SCC

Regards