Problem with Access 2007

[FKlassen]

Hi,

I downloaded a trial version of Access 2007 and it's causing me a lot of
grief.

If I open an application created with Access 2000 - with Access 2007 it
opens and runs fine. Forms load and all controls work as intended.
Then if I try to open it with Access 2000 I get an error message:

The expression On Open you entered as the event property setting produced
the following error: Object or class does not support the set of events.
* The expression may not result in the name of a macro, the name of a user
defined function, or [Event Procedure]
* There may have been an error evaluating the function, event, or macro

If I then hit the OK Button it asks me to input a parameter that normally
gets entered from the main screen once its opened - after I choose to add a
new record or edit an existing one. Its like the query that fills in the
data wants to run before its intended to run.

If I hit OK or CANCEL then I get another error message saying the same thing
about the On Load event.

If it hit OK the form will actually open and focus will go to a control
other than its supposed to. It's a text box and anything I do at this point
causes the On Exit event to cause another similar message.

Now here's the goofy part: If I use Access 2000 to open an "archived"
version of the application - one that has never been opened by Access 2007
it operates as it supposed to.

So it would appear that Access 2007 has somehow altered the code or is doing
something different than Access 2000.

I have tried using the SAVE AS ACCESS 2000...but no luck.

Does anyone have any idea how to overcome this?


FK

 

[ruralguy via AccessMonster.com]

I would start by making sure you have the latest updates to Access 2007.
Office update will check it for you.

Hi,

I downloaded a trial version of Access 2007 and it's causing me a lot of
grief.

If I open an application created with Access 2000 - with Access 2007 it
opens and runs fine. Forms load and all controls work as intended.
Then if I try to open it with Access 2000 I get an error message:

The expression On Open you entered as the event property setting produced
the following error: Object or class does not support the set of events.
* The expression may not result in the name of a macro, the name of a user
defined function, or [Event Procedure]
* There may have been an error evaluating the function, event, or macro

If I then hit the OK Button it asks me to input a parameter that normally
gets entered from the main screen once its opened - after I choose to add a
new record or edit an existing one. Its like the query that fills in the
data wants to run before its intended to run.

If I hit OK or CANCEL then I get another error message saying the same thing
about the On Load event.

If it hit OK the form will actually open and focus will go to a control
other than its supposed to. It's a text box and anything I do at this point
causes the On Exit event to cause another similar message.

Now here's the goofy part: If I use Access 2000 to open an "archived"
version of the application - one that has never been opened by Access 2007
it operates as it supposed to.

So it would appear that Access 2007 has somehow altered the code or is doing
something different than Access 2000.

I have tried using the SAVE AS ACCESS 2000...but no luck.

Does anyone have any idea how to overcome this?

FK

 

[FKlassen]

It worked!

Thanks alot.

I would start by making sure you have the latest updates to Access 2007.
Office update will check it for you.

Hi,

I downloaded a trial version of Access 2007 and it's causing me a lot of
grief.

If I open an application created with Access 2000 - with Access 2007 it
opens and runs fine. Forms load and all controls work as intended.
Then if I try to open it with Access 2000 I get an error message:

The expression On Open you entered as the event property setting produced
the following error: Object or class does not support the set of events.
* The expression may not result in the name of a macro, the name of a user
defined function, or [Event Procedure]
* There may have been an error evaluating the function, event, or macro

If I then hit the OK Button it asks me to input a parameter that normally
gets entered from the main screen once its opened - after I choose to add
a
new record or edit an existing one. Its like the query that fills in the
data wants to run before its intended to run.

If I hit OK or CANCEL then I get another error message saying the same
thing
about the On Load event.

If it hit OK the form will actually open and focus will go to a control
other than its supposed to. It's a text box and anything I do at this
point
causes the On Exit event to cause another similar message.

Now here's the goofy part: If I use Access 2000 to open an "archived"
version of the application - one that has never been opened by Access 2007
it operates as it supposed to.

So it would appear that Access 2007 has somehow altered the code or is
doing
something different than Access 2000.

I have tried using the SAVE AS ACCESS 2000...but no luck.

Does anyone have any idea how to overcome this?

FK

 

[ruralguy via AccessMonster.com]

You're welcome. Thanks for posting back with your success.

It worked!

Thanks alot.

I would start by making sure you have the latest updates to Access 2007.
Office update will check it for you.

[quoted text clipped - 42 lines]

 

[FKlassen]

Unfortunately I spoke too soon.
Problem has come back - and it's worse

After I downloaded the updates (both Office 2007 and 2002 - I thought I was
running MS Office 2000 but it's really 2002) I opened one of my apps with
Access 2002 and it opened perfectly. Then I opened it with 2007 - and ever
since dong that the problem is back. And now what happens is every time I
open an app Windows says it can't find it and then it re-configures either
Office 2007 or 2002 - depending on which version I'm trying to use.

Maybe the two versions are not able to co-exist on the same PC. I guess i
will ahve to uninstall the tyeh 2007 an see if that fixes things. It is
funny though as I have had the rial installed since around the end of
February and this issue just started recently.

*&&$@$ ^%*&^*&^*^% computers.

You're welcome. Thanks for posting back with your success.

It worked!

Thanks alot.

I would start by making sure you have the latest updates to Access 2007.
Office update will check it for you.

[quoted text clipped - 42 lines]

FK

 

[ruralguy via AccessMonster.com]

What you are describing is the Office 2007 coffee break! The two can coexist
on a PC but each time you run "the other version" there is a reconfiguration
that takes place. So after running Access 2002, when you run Access 2007 it
needs to "install" again. After running Access 2007, when you run Access
2002 again it will need to "install". The delay is shorter going from 2007
to 2002 and the updates have made the 2002 to 2007 delay shorter that before
but it still takes time. Sorry.

Unfortunately I spoke too soon.
Problem has come back - and it's worse

After I downloaded the updates (both Office 2007 and 2002 - I thought I was
running MS Office 2000 but it's really 2002) I opened one of my apps with
Access 2002 and it opened perfectly. Then I opened it with 2007 - and ever
since dong that the problem is back. And now what happens is every time I
open an app Windows says it can't find it and then it re-configures either
Office 2007 or 2002 - depending on which version I'm trying to use.

Maybe the two versions are not able to co-exist on the same PC. I guess i
will ahve to uninstall the tyeh 2007 an see if that fixes things. It is
funny though as I have had the rial installed since around the end of
February and this issue just started recently.

*&&$@$ ^%*&^*&^*^% computers.

You're welcome. Thanks for posting back with your success.

[quoted text clipped - 7 lines]

 

[FKlassen]

You are correct about the coffee break...but the strange thing is I still
have the error messages with 2002.
Every event - in the order they occur on opening an application - fires and
causes the same message.
Here's what else I found out: I have another PC in my office that I use for
testing stuff.
I installed the 2007 trial on it and I installed ONLY Access 2000.
The coffee break behaviour still occurs but I do not get the error messages
when I run an app with Access 2000.
Next I will un-install Access 2000 and install Access 2002 and see what
happens.
The other difference is my PC is running Vista and my test PC is XP so that
complicates things too.

What you are describing is the Office 2007 coffee break! The two can
coexist
on a PC but each time you run "the other version" there is a
reconfiguration
that takes place. So after running Access 2002, when you run Access 2007
it
needs to "install" again. After running Access 2007, when you run Access
2002 again it will need to "install". The delay is shorter going from
2007
to 2002 and the updates have made the 2002 to 2007 delay shorter that
before
but it still takes time. Sorry.

Unfortunately I spoke too soon.
Problem has come back - and it's worse

After I downloaded the updates (both Office 2007 and 2002 - I thought I
was
running MS Office 2000 but it's really 2002) I opened one of my apps with
Access 2002 and it opened perfectly. Then I opened it with 2007 - and ever
since dong that the problem is back. And now what happens is every time I
open an app Windows says it can't find it and then it re-configures either
Office 2007 or 2002 - depending on which version I'm trying to use.

Maybe the two versions are not able to co-exist on the same PC. I guess i
will ahve to uninstall the tyeh 2007 an see if that fixes things. It is
funny though as I have had the rial installed since around the end of
February and this issue just started recently.

*&&$@$ ^%*&^*&^*^% computers.

You're welcome. Thanks for posting back with your success.

[quoted text clipped - 7 lines]

FK

 

[ruralguy via AccessMonster.com]

Based on what I've been reading, many things are possible with Vista.

You are correct about the coffee break...but the strange thing is I still
have the error messages with 2002.
Every event - in the order they occur on opening an application - fires and
causes the same message.
Here's what else I found out: I have another PC in my office that I use for
testing stuff.
I installed the 2007 trial on it and I installed ONLY Access 2000.
The coffee break behaviour still occurs but I do not get the error messages
when I run an app with Access 2000.
Next I will un-install Access 2000 and install Access 2002 and see what
happens.
The other difference is my PC is running Vista and my test PC is XP so that
complicates things too.

What you are describing is the Office 2007 coffee break! The two can
coexist

[quoted text clipped - 32 lines]