A2000 & A2003

[Fred Zuckerman]

I have a database on a shared drive. It has user level security (ie: mdw
file). It was created in A2000 and works fine when opened on workstations
with A2000 installed.

Some workstations have A2003 installed. On those workstations there is an
unbound form that continually gives the un-useful message:

"Microsoft Access Has Encountered A Problem And Must Shutdown, We're Sorry
For The Inconvenience"

The message appears after entering data into any of the three unbound
controls and then losing focus. But there are no "on lost focus" events or
"on exit" events.

I have compacted the mdb from both A2000 workstations and A2003
workstations. But it continues to have this trouble on the A2003
workstations and works great on the A2000 workstations.

I have checked the references on the various workstations and they are the
same, except the A2003 workstations have:
Micrososoft Access 11.0 Object Library

while the A2000 workstations have:
Micrososoft Access 9.0 Object Library

The other references are identical:
Visual Basic For Applications
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.5 Library

Does anyone have any sugesstions?
TIA,
Fred Zuckerman

[Harry Skelton]

Fred Zuckerman wrote:

The other references are identical:
Visual Basic For Applications

You need to check which one. There are several different versions. Even
if you cross platform.

OLE Automation
Microsoft DAO 3.6 Object Library

This can pose a problem. Try an older DAO. There is a "compatibil ity"
version available. It is also not wise to mix DAO with ActiveX when
dealing with mixed versions of Access

Microsoft ActiveX Data Objects 2.5 Library

Which one are you going to use? DAO or ADO? Pick one. It will solve
many problems.

You also need to check the versions of the other libraries you may have
loaded. Another problem is the form itself. The version of Microsoft
Office Forms library causes this type of crash. Particularly the
calendar controls. They are bad for crashing...

Create a form with only one control, then go through each of the
controls until you find the one that crashes.

Lastly, sometime Access looses its mind over forms. Create a new form.
Cut all the controls from one form and past to another (on the 2003
system). Then cut and paste the underlaying VB Code. Then try to run
it. If you cannot open the form (because it causes the system to crash)
you can always export it on 2000, to a text based .frm file. Then
import it in the 2003.

However, I still feel that you use a control that is not common to the
Forms library, and/or you are using a calendar control/date picker.
These kill mixed Access platforms. Try to get a third party control, if
one is available.