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

Differences between Access 97 and Access 2000/2003

P: n/a
Hi All,

Our company is migrating from Windows NT to XP and in the process from
Access 97 to Access 2003.
Due to the phased rollout we are faced with a situation where some users are
still on NT while others have been fully upgraded, but all users need to use
the same Access databases.
At first we tried just opening the Access 97 databases with XP but we were
worried that some of the less computer-literate employees may click "yes" on
the "Do you want to convert this database to the latest version" prompt.
The solution we have come up with is to create an exact duplicate of the
database in XP but with all the Tables removed and relinked to the 97
version.
This solution is working well on the whole but there have been a couple of
instances where that database has required a repair.

The main problem we are still having is that my colleagues and I can no
longer make any changes to the database while there are any users in. Is
this a setting which we can change?
For instance, on 97 you could alter a form in the live database and then
save the altered form......XP doesn't seem to allow you to do that.

Any help would be massively appreciated.

Thanks in Advance,

John
Nov 13 '05 #1
Share this Question
Share on Google+
11 Replies


P: n/a
John, as you found, Access 2000 and later do a monolithic save, and there is
no setting to override this.

For other suggestions on adapting to the newer versions, see:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://allenbrowne.com/ser-48.html
(The monolithic save issue is listed as #6 under 'Usability issues'.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"John Ortt" <Jo******@Idontwantspamsonoreturnaddress.com> wrote in message
news:42**********@glkas0286.greenlnk.net...

Our company is migrating from Windows NT to XP and in the process from
Access 97 to Access 2003.
Due to the phased rollout we are faced with a situation where some users
are
still on NT while others have been fully upgraded, but all users need to
use
the same Access databases.
At first we tried just opening the Access 97 databases with XP but we were
worried that some of the less computer-literate employees may click "yes"
on
the "Do you want to convert this database to the latest version" prompt.
The solution we have come up with is to create an exact duplicate of the
database in XP but with all the Tables removed and relinked to the 97
version.
This solution is working well on the whole but there have been a couple of
instances where that database has required a repair.

The main problem we are still having is that my colleagues and I can no
longer make any changes to the database while there are any users in. Is
this a setting which we can change?
For instance, on 97 you could alter a form in the live database and then
save the altered form......XP doesn't seem to allow you to do that.

Any help would be massively appreciated.

Thanks in Advance,

John

Nov 13 '05 #2

P: n/a
Thanks Allen,

No the answer I wanted but still very helpful :)
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:42***********************@per-qv1-newsreader-01.iinet.net.au...
John, as you found, Access 2000 and later do a monolithic save, and there is no setting to override this.

For other suggestions on adapting to the newer versions, see:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://allenbrowne.com/ser-48.html
(The monolithic save issue is listed as #6 under 'Usability issues'.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


Nov 13 '05 #3

P: n/a
"John Ortt" <Jo******@Idontwantspamsonoreturnaddress.com> wrote in message
news:42**********@glkas0286.greenlnk.net...
Hi All,

Our company is migrating from Windows NT to XP and in the process from
Access 97 to Access 2003.
I wonder which company that is.
Due to the phased rollout we are faced with a situation where some users
are
still on NT while others have been fully upgraded, but all users need to
use
the same Access databases.
At first we tried just opening the Access 97 databases with XP but we were
worried that some of the less computer-literate employees may click "yes"
on
the "Do you want to convert this database to the latest version" prompt.
The solution we have come up with is to create an exact duplicate of the
database in XP but with all the Tables removed and relinked to the 97
version.
Seems reasonable.
This solution is working well on the whole but there have been a couple of
instances where that database has required a repair.
I'm not sure that is related to A2k3 linking to an A97 BE.
The main problem we are still having is that my colleagues and I can no
longer make any changes to the database while there are any users in. Is
this a setting which we can change?
For instance, on 97 you could alter a form in the live database and then
save the altered form......XP doesn't seem to allow you to do that.


This is very dangerous practice, far more likely a source of corruption than
linking different versions. You should never attempt to change a FE in the
production environment, you should always work on a development copy and
deploy it to production once testing is complete. You should also ensure
that all users have their own copies of the FE. This would also minimise
the risk of unwanted conversions taking place. Applying user-level security
would stop it in its tracks but is a more long-term solution.

HTH - Keith.
www.keithwilby.com

Nov 13 '05 #4

P: n/a
"Keith" <ke*********@baeAWAYWITHITsystems.com> wrote in
news:42**********@glkas0286.greenlnk.net:
This is very dangerous practice, far more likely a source of
corruption than linking different versions. You should never
attempt to change a FE in the production environment, you should
always work on a development copy and deploy it to production once
testing is complete. You should also ensure that all users have
their own copies of the FE. This would also minimise the risk of
unwanted conversions taking place. Applying user-level security
would stop it in its tracks but is a more long-term solution.


Secondly, each user should have their own copy of the front end, so
if they convert, it won't affect anybody but the single user.

This was true *before* Access 2000, of course.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #5

P: n/a
"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@216.196. 97.142...
"Keith" <ke*********@baeAWAYWITHITsystems.com> wrote in
news:42**********@glkas0286.greenlnk.net:
You should also ensure that all users have
their own copies of the FE. This would also minimise the risk of
unwanted conversions taking place.


Secondly, each user should have their own copy of the front end, so
if they convert, it won't affect anybody but the single user.

Erm, didn't I already say that David? ;-)
Nov 13 '05 #6

P: n/a
Keith wrote:
"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@216.196. 97.142...
"Keith" <ke*********@baeAWAYWITHITsystems.com> wrote in
news:42**********@glkas0286.greenlnk.net:

You should also ensure that all users have
their own copies of the FE. This would also minimise the risk of
unwanted conversions taking place.


Secondly, each user should have their own copy of the front end, so
if they convert, it won't affect anybody but the single user.


Erm, didn't I already say that David? ;-)


Can I just add that all users should have their own copy of the front end.
;-)
--
[OO=00=OO]
Nov 13 '05 #7

P: n/a
Keith wrote:
"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@216.196. 97.142...
"Keith" <ke*********@baeAWAYWITHITsystems.com> wrote in
news:42**********@glkas0286.greenlnk.net:

You should also ensure that all users have
their own copies of the FE. This would also minimise the risk of
unwanted conversions taking place.


Secondly, each user should have their own copy of the front end, so
if they convert, it won't affect anybody but the single user.


Erm, didn't I already say that David? ;-)


Can I just add that all users should have their own copy of the front end.
;-)
--
[OO=00=OO]
Nov 13 '05 #8

P: n/a
"Trevor Best" <no****@besty.org.uk> wrote in message
news:42*********************@news.zen.co.uk...
Secondly, each user should have their own copy of the front end, so
if they convert, it won't affect anybody but the single user.


Erm, didn't I already say that David? ;-)


Can I just add that all users should have their own copy of the front end.
;-)

Can I just say this is the first time I've been on television?
;-p
Nov 13 '05 #9

P: n/a
"Trevor Best" <no****@besty.org.uk> wrote in message
news:42*********************@news.zen.co.uk...
Secondly, each user should have their own copy of the front end, so
if they convert, it won't affect anybody but the single user.


Erm, didn't I already say that David? ;-)


Can I just add that all users should have their own copy of the front end.
;-)

Can I just say this is the first time I've been on television?
;-p
Nov 13 '05 #10

P: n/a
Keith wrote:
"Trevor Best" <no****@besty.org.uk> wrote in message
news:42*********************@news.zen.co.uk...
Secondly, each user should have their own copy of the front end, so
if they convert, it won't affect anybody but the single user.
Erm, didn't I already say that David? ;-)


Can I just add that all users should have their own copy of the front end.
;-)


Can I just say this is the first time I've been on television?
;-p


I normally end up on the telly when I'm drunk... or the sideboard, or
the coffee table...

--
[OO=00=OO]
Nov 13 '05 #11

P: n/a
Keith wrote:
"Trevor Best" <no****@besty.org.uk> wrote in message
news:42*********************@news.zen.co.uk...
Secondly, each user should have their own copy of the front end, so
if they convert, it won't affect anybody but the single user.
Erm, didn't I already say that David? ;-)


Can I just add that all users should have their own copy of the front end.
;-)


Can I just say this is the first time I've been on television?
;-p


I normally end up on the telly when I'm drunk... or the sideboard, or
the coffee table...

--
[OO=00=OO]
Nov 13 '05 #12

This discussion thread is closed

Replies have been disabled for this discussion.