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

access 97 application only works in 2000?

P: n/a
I have an application written in ms access 97. Just recently certain
queries have been giving various errors -- one of which is "there was
an error executing the command".
When I ran the application in access 2000, no errors occurred.
Any ideas? If I open the database file in 2000 it asks me if I want to
convert the database -- so, I know that it is still a 97 database.

Thanks!
skiz

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


P: n/a
A2000 uses a completely different query engine (JET 4) compared to A97 (JET
3.5).

There are several new pieces of functionality that work in JET 4 that are
not in in 3.5.

It could also be a partially corrupted database. You could try getting A97
to rebuild the database for you by following the steps of the first symptom
in this article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

--
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.

"skiz" <on**************@hotmail.com> wrote in message
news:11*********************@o13g2000cwo.googlegro ups.com...
I have an application written in ms access 97. Just recently certain
queries have been giving various errors -- one of which is "there was
an error executing the command".
When I ran the application in access 2000, no errors occurred.
Any ideas? If I open the database file in 2000 it asks me if I want to
convert the database -- so, I know that it is still a 97 database.

Thanks!
skiz

Nov 13 '05 #2

P: n/a
Thanks for the reply on my post!

I tried the repair utility and still does not work.

Can you tell me why the new (access 2000) engine works and not the 97?
Is this because it 'fixes' the corrupted database?

I'm not that ms access savy -- so I'm not sure about re-creating the
whole application...
mmm.
I might try it though -- or just use access 2000 from here on out.
thanks!

Nov 13 '05 #3

P: n/a
Without knowing details of the query, it's not possible to say why it worked
in one version and not another, but corruption is one possible reason.

Getting Access to recreate the database for you is quite a simple task, just
a few minutes work, and worth learning. If you develop heaps, it's something
you need to do quite often.

--
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.

"skiz" <on**************@hotmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
Thanks for the reply on my post!

I tried the repair utility and still does not work.

Can you tell me why the new (access 2000) engine works and not the 97?
Is this because it 'fixes' the corrupted database?

I'm not that ms access savy -- so I'm not sure about re-creating the
whole application...
mmm.
I might try it though -- or just use access 2000 from here on out.
thanks!

Nov 13 '05 #4

P: n/a
Hi again,

I happen to stumble acrossed more information on this problem.
Some users do not get an error and some do.
1) The majority of users have windows xp and access 97 and access 2000
installed and they get errors when they run it under access 97 (they do
not get errors under 2000, but sometimes get sharing violations).
2) Another user has windows 2000 and only access 97 installed and gets
errors.
3) Another user has windows xp and only access 97 installed and it
works.

So, I'm thinking it is something with the workstation setup on each
user's machine that is causing it not to work. I know there are
probably a lot of variables involved here, but any thoughts you have
would be much appreciated!!

thank you for your help so far! :)

Allen Browne wrote:
Without knowing details of the query, it's not possible to say why it worked in one version and not another, but corruption is one possible reason.
Getting Access to recreate the database for you is quite a simple task, just a few minutes work, and worth learning. If you develop heaps, it's something you need to do quite often.

--
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.

"skiz" <on**************@hotmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
Thanks for the reply on my post!

I tried the repair utility and still does not work.

Can you tell me why the new (access 2000) engine works and not the 97? Is this because it 'fixes' the corrupted database?

I'm not that ms access savy -- so I'm not sure about re-creating the whole application...
mmm.
I might try it though -- or just use access 2000 from here on out.
thanks!


Nov 13 '05 #5

P: n/a
skiz wrote:
Hi again,

I happen to stumble acrossed more information on this problem.
Some users do not get an error and some do.


My guess:

A97 and A2000 installations on the same machine can be problematic and
library references get mixed up. If you don't install it correctly,
you've messed up a machine and some, like Albert Kallal, have stated
that the dll hell result can really only be fixed by reformatting the
machine.

I've seen A97 installations referencing the newer DAO 3.6 instead of DAO
3.51 or unable to find DAO 3.51 causing errors in format, left and other
functions. It would not surprise me if the references for Jet might
also be mixed up.

If this application has been altered on such machines,

I'm assuming there's code with this app. If so, open a module and check
your references under tools->references. You should have Microsoft DAO
Library 3.51 Object Library showing, not 3.6.

I've also had considerabe problems with A97 on win XP installations.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Nov 13 '05 #6

P: n/a
Thanks for the reply!
I checked the module library references and they are pointing to 3.51
(not 3.6).
(There was only one module)

Thanks,

Christy

Nov 13 '05 #7

P: n/a
skiz wrote:
Thanks for the reply!
I checked the module library references and they are pointing to 3.51
(not 3.6).
(There was only one module)


On which computer?

On the computers where you are having trouble, create a new A97 mdb.
Create an empty module and do the same reference checks. You'll likely
see 3.6 there. If so, that's your problem: incorrect installation.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Nov 13 '05 #8

P: n/a
My computer is one of the workstations that is getting errors. So, I'm
testing on my machine.
I created a new A97 database and a new module, then went to lib refs
and it has DAO 3.51 checked (3.6 is not listed).

if you have any other ideas that would be great!

Nov 13 '05 #9

P: n/a
skiz wrote:
My computer is one of the workstations that is getting errors. So, I'm
testing on my machine.
I created a new A97 database and a new module, then went to lib refs
and it has DAO 3.51 checked (3.6 is not listed).

if you have any other ideas that would be great!


Along the very same theme I've been parroting endlessly here, incorrect
installtions:

Is this a properly deployed front end mdb? ie, one copy only per
machine? Or is it run off a network, same mdb by multiple machines? If
the latter, check the very same thing you've done for your machine, ie,
the DAO version that gets referenced.

Other than that, I would consider going to A2003. I've simply had far
too much trouble with A97 on win XP to be bothered with it anymore.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Nov 13 '05 #10

P: n/a
The .mdb resides on a network drive and is shared -- so I think you're
right that it is not properly deployed. I checked the lib refs on the
network .mdb modules and it is pointing to 3.51.

I think I will just upgrade the users to A2000 (kinda the standard here
anyways for other apps), since the app seems to work fine using that.

thanks for your help!

Tim Marshall wrote:
skiz wrote:
My computer is one of the workstations that is getting errors. So, I'm testing on my machine.
I created a new A97 database and a new module, then went to lib refs and it has DAO 3.51 checked (3.6 is not listed).

if you have any other ideas that would be great!
Along the very same theme I've been parroting endlessly here,

incorrect installtions:

Is this a properly deployed front end mdb? ie, one copy only per
machine? Or is it run off a network, same mdb by multiple machines? If the latter, check the very same thing you've done for your machine, ie, the DAO version that gets referenced.

Other than that, I would consider going to A2003. I've simply had far too much trouble with A97 on win XP to be bothered with it anymore.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me


Nov 13 '05 #11

This discussion thread is closed

Replies have been disabled for this discussion.