I am developing applications on access xp, but my client only has access 2000. This generally speaking seems to work OK - except that sometimes the buttons (created using the button wizard in xp) don't seem to get recognised in 2000. When I view the code, it recognises it OK, and when I view then save, it seems to work OK.

My question is: what is happening? Why don't things work reliably? Is there some sort of list of things which won't work reliably in 2000? And, most importantly, what should I do about it? I can't get hold of a copy of access 2000.

Any thoughts gratefully received!

Alister

What do you mean with "don't seem to get recognised "? code does not run? do
you get some error message? or just nothing happens?
--
Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com


"Alister Pate" <Alister (E-Mail Removed)> wrote in message
news:0F17B264-F2B2-4FB1-8DBE-(E-Mail Removed)...
> I am developing applications on access xp, but my client only has access
2000. This generally speaking seems to work OK - except that sometimes the
buttons (created using the button wizard in xp) don't seem to get recognised
in 2000. When I view the code, it recognises it OK, and when I view then
save, it seems to work OK.
>
> My question is: what is happening? Why don't things work reliably? Is
there some sort of list of things which won't work reliably in 2000? And,
most importantly, what should I do about it? I can't get hold of a copy of
access 2000.
>
> Any thoughts gratefully received!
>
> Alister

I have a few cases where I created access2000 databases with access 2002
(xp).

And, the end results of the database did have some trouble.

I simply re-installed access 2002, and have not since seen this problem.

So, if your accessXP disk, or install somehow did not work 100%, then that
could very well be the source of your troubles.

I would clean the accessXP disk, and re-install....and further make sure all
the updates to office are installed (don't run any un-patched version..or
any early pre-release version).

I have no idea as to why I had these problems..but they are much like
yours...after loading,a and testing on a a2000 box, simply modify, or
changing the control seemed to fix the problems.

However, I did have to re-install everything on my development pc, and when
I re-installed access 2002, then I never saw the problem again. (so, my
guess is that some corrupting, or some bad installed occurred with the
office 2002. And, for some reason, it would result in a bad a2002 mdb. You
see, I was development on my pc, but did NOT have a2000. I would then use
another pc to create the mde..and that mdb, and mde did have troubles (so,
the only thing could come up with was that my a2002 install was not 100%)).


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(E-Mail Removed)
http://www.attcanada.net/~kallal.msn

Thanks Albert, I'll give that a try

Alex, it gave an error. However, I can't duplicate it because I don't have access to a 2000 access to test it on. But hopefully reinstalling will help.

Thanks to you both for your time.

"Albert D. Kallal" wrote:

> I have a few cases where I created access2000 databases with access 2002
> (xp).
>
> And, the end results of the database did have some trouble.
>
> I simply re-installed access 2002, and have not since seen this problem.
>
> So, if your accessXP disk, or install somehow did not work 100%, then that
> could very well be the source of your troubles.
>
> I would clean the accessXP disk, and re-install....and further make sure all
> the updates to office are installed (don't run any un-patched version..or
> any early pre-release version).
>
> I have no idea as to why I had these problems..but they are much like
> yours...after loading,a and testing on a a2000 box, simply modify, or
> changing the control seemed to fix the problems.
>
> However, I did have to re-install everything on my development pc, and when
> I re-installed access 2002, then I never saw the problem again. (so, my
> guess is that some corrupting, or some bad installed occurred with the
> office 2002. And, for some reason, it would result in a bad a2002 mdb. You
> see, I was development on my pc, but did NOT have a2000. I would then use
> another pc to create the mde..and that mdb, and mde did have troubles (so,
> the only thing could come up with was that my a2002 install was not 100%)).
>
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> (E-Mail Removed)
> http://www.attcanada.net/~kallal.msn
>
>
>