Access 97 on Win XP ? Help ?

[Kevin Jonson]

Hi,

We have upgraded our PC from Win 98 SE to Win XP. Also
changed to MS Office 2000. All went well, except the old
Access 97 database that we had now gives us a strange
message. I don't know Access at all, can anyone help me ?

When I try to open the database in Access 2000, it wants
us to convert or just open. Either option just says

"The Visual Basic for Applications project in the
database is corrupt"

What does this mean, and how do I fix the problem. I
tried installing MS Office 97 again, but this also does
not work. Gives an error about objects. We would prefer
to upgrade to MS Office 2000.

Many thanks
Kev

 

[John Nurick]

Hi Kevin,

The Access 97 database needs to be in good order before it can
successfully be converted. See
http://www.granite.ab.ca/access/conversionproblems.htm
and http://support.microsoft.com/?id=237313.

 

[Tony Toews]

We have upgraded our PC from Win 98 SE to Win XP. Also
changed to MS Office 2000. All went well, except the old
Access 97 database that we had now gives us a strange
message. I don't know Access at all, can anyone help me ?

When I try to open the database in Access 2000, it wants
us to convert or just open. Either option just says

"The Visual Basic for Applications project in the
database is corrupt"

What does this mean, and how do I fix the problem. I
tried installing MS Office 97 again, but this also does
not work. Gives an error about objects.

What's the exact error message when you attempt to open the MDB in
A97?

We would prefer
to upgrade to MS Office 2000.

First thing to do is to make a copy of the MDB. And hopefully you
have a recent backup somewhere.

It sorta sounds like maybe that MDB got partially converted. A
decompile might help. See the Decompile page at my website.

Also try importing into a new MDB, both A97 and A2000. And see if you
can get a clean copy of it that way.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Kevin Jonson]

Hi,

Thanks for your advice. I have downloaded some of the conversion tools, and
found the error.

I have never played with Access before the upgrade from 98 SE to Win XP, so
forgive me if I use the wrong terminology. Client has decided to stay with
Office 97 if that is easier. I un-installed Office 2000, and put Office 97
back on. The problem is that there is an activeX control that is used in
some of the forms etc, that seems to be stored in the file Comdlg32.dll.
The file is dated 1999, and is 172kb on the Win 98 PC's, but it dated 2002,
and is 252kb on the Win XP PC.

I think the problem lies with a button that is used to change dates (ie up
and down button) was stored in the old DLL, but Win XP seems to have an
updated DLL without that button. Is that possible ? What could I do to
correct the problem.

Thanks for all your help. Much appreicated.

Regards
Kevin Jonson

 

[John Nurick]

Hi Kevin,

button that is used to change dates (ie up
and down button)

This sounds like either an UpDown (or Spinner) control, which is just an
up and down button, or else a DTPicker control, which can show up as a
date with up and down buttons next to it or as a little calendar. As far
as I know neither of these uses COMDLG32.DLL, which contains the common
Windows dialogs (File Open etc.). I'm pretty sure taht no controls were
dropped between Windows 98 and XP.

As I understand it, UpDown and the DTPicker are implemented as Windows
functions in COMCTL32.DLL. For use in environments such as VB or Access
forms they are then encapsulated as ActiveX controls, which are usually
contained in .OCX files. The standard VB set of ActiveX controls seem to
be in comctl32.ocx, comct232.ocx and comct332.ocx. I guess that if your
OCX files have got out of sync with COMCTL32.DLL you could get the
problem you're having.

To make things more complicated, third-party OCXs may also wrap the same
common controls. Also, Access forms may have problems with ActiveX
controls that work perfectly in VB forms and other environments, and
different versions of controls may behave differently. I've never been
able to make the DTPicker control work reliably in Access 97, though I
believe other people have.

So I don't have a good answer. Check the dates on the OCXs and if they
are older than the DLL it may be worth looking out for newer versions of
the ActiveX control(s). If that doesn't get you anywhere, I suggest
posting to microsoft.public.access.forms or .forms.coding, where people
know more about controls than I do.

 

[Kevin Jonson]

Hi,

I still have some PC's on the network running Win 98SE, and they can open
the database file across the network fine, so it must be something to do
with the windows operating systems, and the DLL files ? Is there any way I
can open the form across the network, and go into design mode, and determine
the active X control file names that the form uses ?

When I go into design mode, and remove the button, it opens fine on the Win
XP PC, but the user wants the left and right buttons to change the date
field. Is there any other Active X control or button that I could substitute
for it ?

Thanks for your assistance.

Regards
Kev

 

[John Nurick]

Hi Kev,

Why not just use a pair of standard Access buttons with code to adjust
the date up or down?

 

[Kevin Jonson]

The exact message in AC97 is "There is no object in this control". How do I
find out which file the offending Active X control is sitting in ? Is it a
DLL or Ocx file ?