XP - 97 lockup

[Tony Epton]

Got a site where we are still running the front end and back end on an
older machine under access 97 plus a new machine using XP as the front
end.

Only installed the XP version yesterday.

Client is reporting a one off complete lockup of the 97 machine this
morning (sounds like it happened when the XP machine looked at it).
They are back up and running happily at this moment.

Client is very short on details, hence so am I. But they are sounding
pretty hostile so I better get on to this very quickly.

I know my description is very vague but can any one give me a starting
list of gotchas that I could start checking through in the absence of
clear symptoms.

ps - the site is 300 miles away - so all this is via phone.

Many thanks in advance

Tony Epton

[Tony Toews]

ace join_to wa**@iinet.net.au (Tony Epton) wrote:

Client is reporting a one off complete lockup of the 97 machine this
morning (sounds like it happened when the XP machine looked at it).
They are back up and running happily at this moment.

Has the '97 machine ever been a server before? I'd suggest finding a large zipped
file, ie several hundred MB and copy it back and forth several times between the
machines. And see if the file no longer verifies properly or if the system locks up.
This isn't a great test but it's the only one I can think of for right now.

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

[Larry Linson]

The most common problem would be that the Access 2002 (the Access that is
part of Office XP -- there isn't an Access XP) has opened the backend
database for exclusive use.

The best collection of information and links on multiuser issues of which I
am aware is at MVP Tony Toews' site http://www.granite.ab.ca/accsmstr.htm.
If you can't verify that the Access 2002 user has got exclusive use of the
back-end database, that's where I suggest you start.

Larry Linson
Microsoft Access MVP

<ace join_to wa**@iinet.net.au (Tony Epton)> wrote in message
news:40**************@news.m.iinet.net.au...

Got a site where we are still running the front end and back end on an
older machine under access 97 plus a new machine using XP as the front
end.

Only installed the XP version yesterday.

Client is reporting a one off complete lockup of the 97 machine this
morning (sounds like it happened when the XP machine looked at it).
They are back up and running happily at this moment.

Client is very short on details, hence so am I. But they are sounding
pretty hostile so I better get on to this very quickly.

I know my description is very vague but can any one give me a starting
list of gotchas that I could start checking through in the absence of
clear symptoms.

ps - the site is 300 miles away - so all this is via phone.

Many thanks in advance

Tony Epton

[Tony Epton]

>Has the '97 machine ever been a server before?

Thanks for that

I think it had the same role before - just an older machine using
Access 97 was pointing at it before.

In fact with the new machine - our first attempt was to install Office
2002 (sans Access 2002) along with Acess 97.

I have a couple of other sites where this runs successfully - but
didn't in this case.

Forget the error messages when we tried this - but they were
indicative of mismatched dlls

Next I tried getting the users to install Access 2002 and I converted
the 97 front end database to 2002.

Maybe all this is indicating a need to wipe to the new machine and try
again.
I'm almost inclined to get them to revert the new machine back to 97.

Any opinion ?

Not keen to move the 97machine forward to Office XP as this will only
cause the client more expense and disruption and cannot guarantee a
fix - plus the client's getting a bit toey about the whole journey.

Many thanks
Tony