Access Charts - SR-1 v/s SP-3

  • Thread starter Thread starter Willem
  • Start date Start date
W

Willem

When Creating chart in ACCESS 2000 with SP-3 there is a
stuff up with the chart design. You have to do it to
understand what it does - it is either over- or
undersized for the area - and you cannot resize it, and
believe me, I have tried everything to get it right.

Designing a chart with Access 2000 SR-1 works, BUT when I
compact or MDE the database, it gives the following error:
"Microsoft Access was unable to create an mde Database"
Creating an mde with Access 2000 SP-3, works. (after I
have created it with Access 2000 SR-1)

The fact that is does not want to mde has nothing to do
with code that is not in use etc. I have pinpointed the
error to the chart - it only happens with this chart
present.

When going into the database after this and clicking on
any button, it says:-
"Error accessing file. Network connection may have been
lost."

The only way to recover from this is to fall back to the
previous backup before the mde or compact option was
executed. I then compact and mde it on Access 2000 SP-3,
and run it successfully on Access 2000 SR-1.

A chart created in Access 2000 SR-1, does not display
properly in Access 2000 SP-3.
 
Willem:

There's a bug in Access 2000, that wasn't resolved until SP3, that can
result on a system where a certain version of VB 6 (a later version
installed by a program other than Access) that will result in the "Network
Connection Lost" problem. Its corruption in the compiled VB within the db;
and pretty much hoses the database objects that contain code. It occurs
when you import or delete forms, report, modules or classes from a DB and
fail to compile it before you close the file; resulting in corruption.

While we've never had a problem with working with Graph in an SP3
environment, if you feel the need to work in an SP1 environment you must
compile before you close the db each time to avoid the VB corruption
problem.

Once in a while you can open the vb module but it won't compile (with the
Network connection problem). If you don't have a backup, you can save most
of the file by copying out the code into text files, and setting each each
form / report's "Has Module" property to false, which will delete the code.
Drastic but it can save design work rather than doing a full re-creation.
 
Back
Top