Problems with databases in transition from Access 2002 to Access X

M

MacNut

Hello,

Is there some sort of "bug" when transitioning from Office 2002 to Office XP
when it comes to functionality of databases? With this application I
designed, the command buttons, SOLELY for opening up reports does NOT
function. Nothing happens, and then a message pops up saying "The openreport
action was cancelled." I even changed the command buttons to run macros to
open those reports INSTEAD of event procedures....but still does not work.
Anyone have this problem before? If so, what do I do to correct this?

Thank you.
MN
 
V

Van T. Dinh

Office 2002 *is* Office XP!

It sounds more like problems in your database. For example, you may have
coded the NoData Event to cancel the opening of the Report. When your
CommandButton_Click Event executes and no data is found, the opening of your
Report is cancelled and the the CommandButton_Click Event will return the
posted error (error number 2501, I think) unless you trap and handle this
error.
 
T

Tom Wickerath

Hi MacNut,

I've been bitten by the same issue, approximately 5% of the time, when I
send a database uses the Access 2000 file format to an Access 2000 user. I do
most of my work using Access 2002. The database is compiled and works great
in Access 2002. I zip it up and sent it to another user who happens to have
Access 2000. They report back that the switchboard command buttons are dead.
Nothing happens when they click on them. I open the same database using
Access 2000 and I'm able to confirm that the damn command buttons are dead.
The database continues to work great when I reopen it in Access 2002. Again,
this has happened to me approximately 5% of the time (which is too often, if
you ask me).

Using the undocumented /decompile switch with Access 2000 does not fix the
problem. The only way that I've been able to fix this issue is to create a
brand new database using Access 2000, and then import all objects from the
source database into the new database. The experts at FMS recommend importing
each group of objects separately (ie. all tables, then all queries, then all
forms, etc. as separate import operations). Set the references in the new
database to match the source database. Compile the project. Set the startup
options to match the source database as well. This has always restored full
functionality in Access 2000 when I have carried out these steps. In fact,
many developers make it a regular habit to import all objects into a new
container, as I have just described, before deploying to a client.

One can only conclude that some type of corruption exists in the file, which
is not fixed by discarding the compiled "P" code. It's certainly reasonable
to assume that a similar problem could exist for opening the same file in
Access 2003, after having worked on it using Access 2002.

Tom
_______________________________________

:

Hello,

Is there some sort of "bug" when transitioning from Office 2002 to Office XP
when it comes to functionality of databases? With this application I
designed, the command buttons, SOLELY for opening up reports does NOT
function. Nothing happens, and then a message pops up saying "The openreport
action was cancelled." I even changed the command buttons to run macros to
open those reports INSTEAD of event procedures....but still does not work.
Anyone have this problem before? If so, what do I do to correct this?

Thank you.
MN
 
M

MacNut

Tom,

Thanks for that response. I was wondering if others had problems like this
as well. Sometimes it works ok, and sometimes something screws up. What you
said makes sense and I hope that I won't have to do that for all my
databases!!

Thanks for the info!
MN
 
S

Spottie

We just upgraded to Office 2007 and the first problem I found is command
buttons in my existing databases won't open other forms as they did before.
I tried creating a new button to open the form. Like the post above,
"nothing happens". I don't even get an error message. So far, command
buttons to open reports works. I'll try building a new db and importing
everything.
 
H

hor vannara

Spottie said:
We just upgraded to Office 2007 and the first problem I found is command
buttons in my existing databases won't open other forms as they did
before.
I tried creating a new button to open the form. Like the post above,
"nothing happens". I don't even get an error message. So far, command
buttons to open reports works. I'll try building a new db and importing
everything.
Click to expand...
 
Top