Program not running the same after converting from access 2.0 access 2000

[Guest]

I just converted an access 2.0 program to an access 2000 program. I am using access 2002 for this conversion. I notice that as I go down my application forms and come back up using the button control to close the current form, I now a query prompt asking me for a value instead of bringing back directly to the prior form. This does not happen all the time, but is consistent in the specific form closes where it happens. I am using a XP operating system. Can anyone explain what might be happening.

 

[Albert D. Kallal]

Does all the code compile correctly?

Things have changed a lot since version 2.0 (that is 12 years old...and I
doubt that you are using or convent any other software from 12 years ago! We
are talking BEFORE windows 95 even came out!

We are talking about a time before the internet even existed. In fact, we
are talking about a period where most computers where not even running
windows! In terms of computer years...you are going back centuries!

However, a few things:

I would first try can compile the code, and see if any errors come up. Do
any errors come up when you compile the code?

And, I would take a look at the close event code for the form? What does it
do? (or, perhaps look at the on activate, or on got focus of the form below
the one that is just being closed).

Do you have an experienced access developer on hand, or are you just jumping
in and trying to covert a database application with code that was written
many years ago? It sounds to me like you need some help here?

If you don't have any access experience, then I think it is rather risky to
convert a application as such without some prior learning, or at least
having someone with good ms-access development skills.

I suppose you could just continue to run access 2.0? It is a rather
stunning achievement on the part of Microsoft's that old programs like
access 2.0 still work on new pc's.

Access 2.0 will still run on a new pc, and if you look at companies like
apple computer...old stuff does NOT run, and you have to throw it out.
Apple has done this many time, yet Microsoft continues to allow those old
systems to be installed, and still run!

I do think it is a good idea to upgrade from access 2.0 (however, we must
give credit where due...and access 2.0 still does work on a new pc!...so you
could do nothing...and use 2.0!)

However, I would first try and compile your code. If the code compiles
ok...then I would start looking at the event code for the forms in
question...

Good luck!

 

[Guest]

Yes this is a very old application. Unfortunately, the company that is using this application has sent it out to many customers in the past. This company is now standardizing on Windows 2000 and once this application converted as is. The company sent me an access 2000 version that they tried to get working but they could not get it to compile cleanly. I obtained a white paper for converting access 2.02 access 97 which indicated various changes in the programming code. I made every one of these changes and got the program to compile cleanly. Even though I am using access 2002, when looking at tools database convert it to show me that it now thinks this application is access 2000. I checked out all of the data that is displayed between the Microsoft access 2 and the access 2000 converted program and the results are the same in both. As a matter of fact, when the converted access 2000 version was sent back to the company it works great. It does not have the strange query type " enter value for xxx field" that I see when I close the current form. The close button I use just goes to an on click subroutine that issues DoCmd.Close. I have also checked out the on activate subroutine from the form that shows up once the current form is close and found nothing there that would be a problem. Actually, I can't just click OK to the query like pop up that occurs after the current close form has taken place, and it gets me back to the form I want.

I am surprised that it works fine on his company's computer system that is using Windows 2000, but it is working differently when using Windows XP and the Microsoft access 2002 version.

 

[Arvin Meyer]

I have encountered this bug. You are correct, it only happens on Win XP and
Access 2002. The best that I can figure out is that it happens between
Access and the OS messaging system.

You can work around the problem by restoring the form just before closing:

DoCmd.Restore
DoCmd.Close
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

Yes this is a very old application. Unfortunately, the company that is

using this application has sent it out to many customers in the past. This
company is now standardizing on Windows 2000 and once this application
converted as is. The company sent me an access 2000 version that they tried
to get working but they could not get it to compile cleanly. I obtained a
white paper for converting access 2.02 access 97 which indicated various
changes in the programming code. I made every one of these changes and got
the program to compile cleanly. Even though I am using access 2002, when
looking at tools database convert it to show me that it now thinks this
application is access 2000. I checked out all of the data that is displayed
between the Microsoft access 2 and the access 2000 converted program and the
results are the same in both. As a matter of fact, when the converted
access 2000 version was sent back to the company it works great. It does
not have the strange query type " enter value for xxx field" that I see when
I close the current form. The close button I use just goes to an on click
subroutine that issues DoCmd.Close. I have also checked out the on activate
subroutine from the form that shows up once the current form is close and
found nothing there that would be a problem. Actually, I can't just click
OK to the query like pop up that occurs after the current close form has
taken place, and it gets me back to the form I want.

I am surprised that it works fine on his company's computer system that is

using Windows 2000, but it is working differently when using Windows XP and
the Microsoft access 2002 version.