The Visual Basic for Applications Project in the database is corrupt

[Harris]

Can anyone please help?
I have read the postings on the error "The Visual Basic for
Applications Project in the database is corrupt" but none report the
particular problem I am experiencing, i.e., this error only occurs
running my program on computers of some of my clients.

To elaborate: I have a program that is being used by around 60 clients
all over the world. My program is an mde file in Access2003. It works
absolutely without hitch on the 5 computers in our office (running
Windows XP), and on all but 3 of my clients. The program is
"free-standing", i.e., not running via a network/server. However the
same program installed on 3 of my clients' computers results in this
error when they start the program. They have reinstalled the program,
I have sent them a new installation, (following decompiling and
recompiling the program) but to no avail. The same installation
package installed on my systems, and on a new laptop, runs perfectly
correctly.
Any ideas?
Thanks
Harris

[Allen Browne]

Is it possible that these clients are running Access 2002?

Although A20002 and 2003 use the same file format, they compile the code
differently, and you do get that (not very helpful) error message if you
create an MDE in A2003 and try to run it under A2002.

If that's not the issue, is this a runtime installation? If so, you may need
to release different runtimes for different operating systems, e.g. one for
Windows 98 machines (created on a Win98 installation) and a different one
for Win XP machines (created under Win XP).

It would also be worth checking that the clients have applied the service
packs to their version of Office and to JET 4, including the runtime service
pack that's named something like ART...

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Harris" <ha****@zingsolutions.com> wrote in message
news:6a*************************@posting.google.co m...

Can anyone please help?
I have read the postings on the error "The Visual Basic for
Applications Project in the database is corrupt" but none report the
particular problem I am experiencing, i.e., this error only occurs
running my program on computers of some of my clients.

To elaborate: I have a program that is being used by around 60 clients
all over the world. My program is an mde file in Access2003. It works
absolutely without hitch on the 5 computers in our office (running
Windows XP), and on all but 3 of my clients. The program is
"free-standing", i.e., not running via a network/server. However the
same program installed on 3 of my clients' computers results in this
error when they start the program. They have reinstalled the program,
I have sent them a new installation, (following decompiling and
recompiling the program) but to no avail. The same installation
package installed on my systems, and on a new laptop, runs perfectly
correctly.
Any ideas?
Thanks
Harris

[Harris]

> Is it possible that these clients are running Access 2002?

Although A20002 and 2003 use the same file format, they compile the code
differently, and you do get that (not very helpful) error message if you
create an MDE in A2003 and try to run it under A2002.

If that's not the issue, is this a runtime installation? If so, you may need
to release different runtimes for different operating systems, e.g. one for
Windows 98 machines (created on a Win98 installation) and a different one
for Win XP machines (created under Win XP).

It would also be worth checking that the clients have applied the service
packs to their version of Office and to JET 4, including the runtime service
pack that's named something like ART...

This is a good suggestion but according to my clients they are running
2003. I need to double check. It is not a runtime installation -
however I do supply a 2003 runtime module that can be installed if
they do not have Access installed. I need to follow up on whether they
have installed the service packs and to Jet4, but I do know that I had
asked 1 client to do so, and the error persists. Thanks for
highlighting these issues.
Harris

[Allen Browne]

What we do is include a couple of text boxes on our HelpAbout form, with
test boxes like:
=fGetProductVersion(SysCmd(9) & "msaccess.exe")
=fGetProductVersion(fReturnSysDir() & "\msjet40.dll")

When the user calls you for support, they can then give you the information
to confirm their version and service pack of Office and JET 4.

The functions are from:
http://www.mvps.org/access/api/api0065.htm
http://www.mvps.org/access/api/api0010.htm

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Harris" <ha****@zingsolutions.com> wrote in message
news:6a**************************@posting.google.c om...

Is it possible that these clients are running Access 2002?

Although A20002 and 2003 use the same file format, they compile the code
differently, and you do get that (not very helpful) error message if you
create an MDE in A2003 and try to run it under A2002.

If that's not the issue, is this a runtime installation? If so, you may
need
to release different runtimes for different operating systems, e.g. one
for
Windows 98 machines (created on a Win98 installation) and a different one
for Win XP machines (created under Win XP).

It would also be worth checking that the clients have applied the service
packs to their version of Office and to JET 4, including the runtime
service
pack that's named something like ART...

This is a good suggestion but according to my clients they are running
2003. I need to double check. It is not a runtime installation -
however I do supply a 2003 runtime module that can be installed if
they do not have Access installed. I need to follow up on whether they
have installed the service packs and to Jet4, but I do know that I had
asked 1 client to do so, and the error persists. Thanks for
highlighting these issues.
Harris

[Harris]

Allen,

Thanks very much for your input, it was also very valuable. I sent a
small app to my client to check these details, and found that she was
running AccessXP without any service pack installations- I think this
is crucial information as I can now ask her to install the service
packs and retry the software. Thanks a ton for all the input to both
of you!
Harris