By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,762 Members | 1,845 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,762 IT Pros & Developers. It's quick & easy.

Problem running Access97 on XP

P: n/a
Hi,
has anybody come across a solution to running an Access97 database on
Windows XP. The situation I have is an Access 97 database that runs
perfectly from Win95/98 clients running Access97, the database sits on
a Windows2000 server to which everyone has full NTFS access rights.

The problem is the WinXP and Win2k clients which appear to run fine
(also running Access97) in reading any existing data but as soon as
you attempt to edit a field the cursor sits in the field and a message
appears at the bottom LH corner of the program saying 'This Recordset
is not updateable'. I have checked the NTFS security settings on
everything that I can to give everybody full rights(both server and
client) and have given users local admin rights on their pc's but
still to luck.

I know somebody will say it's not a supported solution (XP and 2k
running Office97) but the Access database is bespoke and can't be
easily migrated to office 2k (the company that did it have gone to the
wall and left no development info behind). Thanks to anybody who has
any pointers to help solve this tricky situation.

Chris
Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Did you copy it via CD and not change the file proprerties to read only
false

Phil

"Chris Dugan" <cf******@yahoo.com> wrote in message
news:82**************************@posting.google.c om...
Hi,
has anybody come across a solution to running an Access97 database on
Windows XP. The situation I have is an Access 97 database that runs
perfectly from Win95/98 clients running Access97, the database sits on
a Windows2000 server to which everyone has full NTFS access rights.

The problem is the WinXP and Win2k clients which appear to run fine
(also running Access97) in reading any existing data but as soon as
you attempt to edit a field the cursor sits in the field and a message
appears at the bottom LH corner of the program saying 'This Recordset
is not updateable'. I have checked the NTFS security settings on
everything that I can to give everybody full rights(both server and
client) and have given users local admin rights on their pc's but
still to luck.

I know somebody will say it's not a supported solution (XP and 2k
running Office97) but the Access database is bespoke and can't be
easily migrated to office 2k (the company that did it have gone to the
wall and left no development info behind). Thanks to anybody who has
any pointers to help solve this tricky situation.

Chris

Nov 12 '05 #2

P: n/a
Hi Phil,

No the database sits on a server, it is the same one that is reached
from the win 95 and 98 clients with no problems, that (read only
attribute) and the NTFS file permissions are what i have checked so far
and as I don't really understand the internals of Access i'm a bit stuck
on where to proceed.

Chris

Remove obvious to reply

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 12 '05 #3

P: n/a
cf******@yahoo.com (Chris Dugan) wrote in message news:<82**************************@posting.google. com>...
Hi,
has anybody come across a solution to running an Access97 database on
Windows XP. The situation I have is an Access 97 database that runs
perfectly from Win95/98 clients running Access97, the database sits on
a Windows2000 server to which everyone has full NTFS access rights.

The problem is the WinXP and Win2k clients which appear to run fine
(also running Access97) in reading any existing data but as soon as
you attempt to edit a field the cursor sits in the field and a message
appears at the bottom LH corner of the program saying 'This Recordset
is not updateable'. I have checked the NTFS security settings on
everything that I can to give everybody full rights(both server and
client) and have given users local admin rights on their pc's but
still to luck.

I know somebody will say it's not a supported solution (XP and 2k
running Office97) but the Access database is bespoke and can't be
easily migrated to office 2k (the company that did it have gone to the
wall and left no development info behind). Thanks to anybody who has
any pointers to help solve this tricky situation.


We run multiple Access 97 applications on Windows XP clients connected
to a Windows 2000 server with no problems at all. Some of these are
split applications, i.e., front end resides on XP desktop and back end
resides on server, and a couple of them are all-in-one databases that
reside strictly on the server (not my preference but these were
supplied by outside sources and we have no control over whether or not
they're split). Regardless, all of them run fine without the problems
you describe. I'm not aware of any statement by Microsoft or anyone
else stating that this is 'not a supported solution'. I think there's
something going on with your Access installation or your specific
application that's the problem. Try putting the northwind database
supplied with Access 97 on your server and see if you can update it
from the XP clients. If not, I suspect there's an issue with your
Access installation. Have you installed all of the latest Office 97,
Windows XP, and 2000 Server service packs? I would definitely do all
of these if you haven't yet done so. In fact, I seem to recall some
kind of file locking problem addressed by a service pack for Windows
2000 server, but my memory is hazy...

HTH,
Bruce
Nov 12 '05 #4

P: n/a
br***@aristotle.net (Bruce) wrote in message news:<d3**************************@posting.google. com>...
<snip>
We run multiple Access 97 applications on Windows XP clients connected
to a Windows 2000 server with no problems at all. Some of these are
split applications, i.e., front end resides on XP desktop and back end
resides on server, and a couple of them are all-in-one databases that
reside strictly on the server (not my preference but these were
supplied by outside sources and we have no control over whether or not
they're split). Regardless, all of them run fine without the problems
you describe. I'm not aware of any statement by Microsoft or anyone
else stating that this is 'not a supported solution'. I think there's
something going on with your Access installation or your specific
application that's the problem. Try putting the northwind database
supplied with Access 97 on your server and see if you can update it
from the XP clients. If not, I suspect there's an issue with your
Access installation. Have you installed all of the latest Office 97,
Windows XP, and 2000 Server service packs? I would definitely do all
of these if you haven't yet done so. In fact, I seem to recall some
kind of file locking problem addressed by a service pack for Windows
2000 server, but my memory is hazy...

HTH,
Bruce


Thanks Bruce, that might be it (the file locking issue). I also found
out about a registry fix for 2k/xp that allows for a plain text
password for the lanman wkstn service which might also be something to
look at.

The file locking was a reg hack that can be done on any version of
Win2k but now you mention it I also have a similar recollection of
either sp3 or 4 having further fixes for that problem.

The app runs as a split db not all residing on the server but that's
about all the info I can give you on it. What I meant by 'not a
supported solution' was that MS have not ested the combination and so
won't provide any support, so usually neither will any of their
partners.

Thanks again,

Chris
Nov 12 '05 #5

P: n/a
On 5 Nov 2003 03:02:17 -0800, cf******@yahoo.com (Chris Dugan) wrote:

Hi Chris,

We rum both Access97 and Access2002 at the same time on our XP
systems. The solution to this installation is in the Microsoft
Knowledge base article 241141

Regards,

Phil

Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.