Damaged ADP?

R

Ralph Schlosser

Hello NG,



I develop an Access-2002-ADP. Its size is about 50 MB and it contains

about 600 forms, 150 reports and 80 modules (40 class modules). That means

there are less than 1000 modules, the limit specified by MS including form-
and

report-modules. Thus this limit can't be the reason of the following
problem:



When I try to save the VBA-project after compiling it I get an "save
operation

failed" error (translated from German, I don't know the original English
message).

When this error occurred the project got completely corrupted because it's
not

possible to open any module.



I suspected a file-corruption of the ADP and tried the following steps:

- decompile / compact / compile / save ==> no success

- import all access objects in an empty ADP ==> no success

- searching for damaged objects ==> no success

the interesting thing is, it works when I delete about 40 forms or reports

(it doesn't matter which forms / reports I delete)

- reconstruction of all access objects in an empty ADP (automated with VBA)

==> no success



And now the most surprising thing: compile and save works perfectly

on Win98. It doesn't work on Win2K, Win2K SP3, Win2K SP4, WinXP and

WinXP SP1 platforms. The problem doesn't depend on Office XP service

packs or installed MDAC versions.



BTW: Access 2003 shows the same error message on Win2K and WinXP.



Any ideas or comments? Thanks in advance.



Ralph.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top