Access 2003 Downwards Compatibility

  • Thread starter Thread starter Siegfried Kaelbert
  • Start date Start date
S

Siegfried Kaelbert

Dear All,
I programmed a large database (65,000 records) in MSAccess
2000. I added a lot of event procedures to the forms in
order to display the contents of tables and queries as
desired. Under Office 2000 these procedures work properly.
Now I changed to Office 2003 and got MSAccess 2003 on my
computer. I had to experience that now these procedures
added to the forms and e.g. text boxes do not work
anymore. When these procedures are called a large fault
message is displayed. The form will be shown without the
data to be filled in by the procedures.
Is there a solution to overcome the problem or is Access
2003 not downwards compatible?
Thanks and best regards
Siegfried
 
A2003 works directly with an A2000 file, so the problem you are experiencing
is not a compatibility one.

What does the "large fault message" say? It may provide clues as to what is
wrong.

Does your code compile? (Compile on Debug menu, from a code window).

There could be a problem with references. Details:
http://members.iinet.net.au/~allenbrowne/ser-38.html

In Access 2003, you may receive annoying messages that tell you your
database is unsafe every time you open it. Lower your macro security
setting:
Tools | Macro | Security | Low
If you do not see that menu option, right-click the toolbar area, customize,
and reset the Menu Bar. For more information, see:
http://office.microsoft.com/assista...3&CTT=8&Origin=EC011081751033&Product=acc2003
 
Hi, Allen,
It is not a matter of the security level. I changed the
level of protection to "Low" but the problem persists.
Here now the fault message:

Microsoft Office Access

The expression On Click you entered as the event property
setting produced the following error: A problem occured
While Microsoft Access was communicating with the OLE
Server or ActiveX control.

*The expression may not result in the name of a macro, the
name of an user-defined function, or [Event Procedure].
*There may have been an error evaluating the function,
event, or macro.

This was the error message I receive. I have the database
(about 260 Mbytes) on CD. When I insert the CD in a system
running on Office 2000 the database works properly in all
functions. When I try the same CD at Office 2003 I face
the reported problem.
Therefore I was thinking about a downwards compatibility
problem.
I have no idea how to overcome the problem and appreciate
very much your help.
With best regards
Sieg
 
Okay, the message can indicate a partially corrupted database. And yes, it
is possible for a partically corrupted database to work in one version and
not in another.

To try to recover it:
1. Open it in Access 2000.

2 Uncheck the boxes under: Tools | Options | General | Name AutoCorrect.

3 Compact the database: Tools | Database Utilties | Compact.

4 Close Access, and decompile a copy of the database by entering something
like this at the command prompt while Access is not running. It is all one
line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

5. Open in A2000 again. Open a code window. Remove any references you do not
need. If you are not sure which you need, see:
http://members.iinet.net.au/~allenbrowne/ser-38.html

6. Check that the application compiles. From the code window: Debug |
Compile.

7. Compact again.

8. Make a copy of the mdb file. Open the copy in A2003. Open a code window,
and choose References from the Tools menu. Check that none are marked
"MISSING". Then check that it still compiles.

9. Test.

If that still does not work, try following the 6 steps for the first symptom
Recovering from Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-47.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Siegfried Kaelbert said:
Hi, Allen,
It is not a matter of the security level. I changed the
level of protection to "Low" but the problem persists.
Here now the fault message:

Microsoft Office Access

The expression On Click you entered as the event property
setting produced the following error: A problem occured
While Microsoft Access was communicating with the OLE
Server or ActiveX control.

*The expression may not result in the name of a macro, the
name of an user-defined function, or [Event Procedure].
*There may have been an error evaluating the function,
event, or macro.

This was the error message I receive. I have the database
(about 260 Mbytes) on CD. When I insert the CD in a system
running on Office 2000 the database works properly in all
functions. When I try the same CD at Office 2003 I face
the reported problem.
Therefore I was thinking about a downwards compatibility
problem.
I have no idea how to overcome the problem and appreciate
very much your help.
With best regards
Sieg



-----Original Message-----
A2003 works directly with an A2000 file, so the problem you are experiencing
is not a compatibility one.

What does the "large fault message" say? It may provide clues as to what is
wrong.

Does your code compile? (Compile on Debug menu, from a code window).

There could be a problem with references. Details:
http://members.iinet.net.au/~allenbrowne/ser-38.html

In Access 2003, you may receive annoying messages that tell you your
database is unsafe every time you open it. Lower your macro security
setting:
Tools | Macro | Security | Low
If you do not see that menu option, right-click the toolbar area, customize,
and reset the Menu Bar. For more information, see:
http://office.microsoft.com/assistance/preview.aspx? AssetID=HP010504321033&CTT=8&Origin=EC011081751033&Product=
acc2003
Click to expand...
Click to expand...
 
I have the same problem with a newly created database
under ACCESS 2003 (nothing to do with conversion or
version compatibility). You add an event procedure to the
load event on a form (or any other event handler). Even if
you do not type anything or just the line 'Msgbox "Hello
World"' and you get that error message. Remove the code
and the form is OK.
In my years of programming with ACCESS, this is the
strangest thing I have seen. I am even thinking of going
back to office 2002.

HABIB.

-----Original Message-----
Okay, the message can indicate a partially corrupted database. And yes, it
is possible for a partically corrupted database to work in one version and
not in another.

To try to recover it:
1. Open it in Access 2000.

2 Uncheck the boxes under: Tools | Options | General | Name AutoCorrect.

3 Compact the database: Tools | Database Utilties | Compact.

4 Close Access, and decompile a copy of the database by entering something
like this at the command prompt while Access is not running. It is all one
line, and include the quotes:
"c:\Program Files\Microsoft
Click to expand...
office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

5. Open in A2000 again. Open a code window. Remove any references you do not
need. If you are not sure which you need, see:
http://members.iinet.net.au/~allenbrowne/ser-38.html

6. Check that the application compiles. From the code window: Debug |
Compile.

7. Compact again.

8. Make a copy of the mdb file. Open the copy in A2003. Open a code window,
and choose References from the Tools menu. Check that none are marked
"MISSING". Then check that it still compiles.

9. Test.

If that still does not work, try following the 6 steps for the first symptom
Recovering from Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-47.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Hi, Allen,
It is not a matter of the security level. I changed the
level of protection to "Low" but the problem persists.
Here now the fault message:

Microsoft Office Access

The expression On Click you entered as the event property
setting produced the following error: A problem occured
While Microsoft Access was communicating with the OLE
Server or ActiveX control.

*The expression may not result in the name of a macro, the
name of an user-defined function, or [Event Procedure].
*There may have been an error evaluating the function,
event, or macro.

This was the error message I receive. I have the database
(about 260 Mbytes) on CD. When I insert the CD in a system
running on Office 2000 the database works properly in all
functions. When I try the same CD at Office 2003 I face
the reported problem.
Therefore I was thinking about a downwards compatibility
problem.
I have no idea how to overcome the problem and appreciate
very much your help.
With best regards
Sieg



-----Original Message-----
A2003 works directly with an A2000 file, so the problem you are experiencing
is not a compatibility one.

What does the "large fault message" say? It may provide clues as to what is
wrong.

Does your code compile? (Compile on Debug menu, from a code window).

There could be a problem with references. Details:
http://members.iinet.net.au/~allenbrowne/ser-38.html

In Access 2003, you may receive annoying messages that tell you your
database is unsafe every time you open it. Lower your macro security
setting:
Tools | Macro | Security | Low
If you do not see that menu option, right-click the toolbar area, customize,
and reset the Menu Bar. For more information, see:
http://office.microsoft.com/assistance/preview.aspx?
Click to expand...
AssetID=HP010504321033&CTT=8&Origin=EC011081751033&Product=
acc2003
Dear All,
I programmed a large database (65,000 records) in MSAccess
2000. I added a lot of event procedures to the forms in
order to display the contents of tables and queries as
desired. Under Office 2000 these procedures work properly.
Now I changed to Office 2003 and got MSAccess 2003 on my
computer. I had to experience that now these procedures
added to the forms and e.g. text boxes do not work
anymore. When these procedures are called a large fault
message is displayed. The form will be shown without the
data to be filled in by the procedures.
Is there a solution to overcome the problem or is Access
2003 not downwards compatible?
Thanks and best regards
Siegfried
Click to expand...
Click to expand...


.
Click to expand...
 
Hello Habib

Access 2003 is *much* more stable than A2002.

If you receive the error on *any* line of code, then it is probably an issue
with references:
http://members.iinet.net.au/~allenbrowne/ser-38.html
or with sandbox mode:
http://office.microsoft.com/assista...3&CTT=8&Origin=EC011081751033&Product=acc2003

Name AutoCorrect could also mess things up, but not that quickly:
http://members.iinet.net.au/~allenbrowne/bug-03.html

If you have not yet applied SP1 for Office 2003, that would be a good idea,
but again the problem you describe is more severe than the patch could
address.
 
Hi Allen,
Thank you very much for your valuable hints. I'll try
them out on Saturday. I live in Saudi Arabia and there is
Thursday and Friday the weekend. My Laptop at home I left
in Office 2000. Only my computer at work is on Office
2003.
I'll keep you informed.
With regards
Siegfried
-----Original Message-----
Okay, the message can indicate a partially corrupted database. And yes, it
is possible for a partically corrupted database to work in one version and
not in another.

To try to recover it:
1. Open it in Access 2000.

2 Uncheck the boxes under: Tools | Options | General | Name AutoCorrect.

3 Compact the database: Tools | Database Utilties | Compact.

4 Close Access, and decompile a copy of the database by entering something
like this at the command prompt while Access is not running. It is all one
line, and include the quotes:
"c:\Program Files\Microsoft
Click to expand...
office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

5. Open in A2000 again. Open a code window. Remove any references you do not
need. If you are not sure which you need, see:
http://members.iinet.net.au/~allenbrowne/ser-38.html

6. Check that the application compiles. From the code window: Debug |
Compile.

7. Compact again.

8. Make a copy of the mdb file. Open the copy in A2003. Open a code window,
and choose References from the Tools menu. Check that none are marked
"MISSING". Then check that it still compiles.

9. Test.

If that still does not work, try following the 6 steps for the first symptom
Recovering from Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-47.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Hi, Allen,
It is not a matter of the security level. I changed the
level of protection to "Low" but the problem persists.
Here now the fault message:

Microsoft Office Access

The expression On Click you entered as the event property
setting produced the following error: A problem occured
While Microsoft Access was communicating with the OLE
Server or ActiveX control.

*The expression may not result in the name of a macro, the
name of an user-defined function, or [Event Procedure].
*There may have been an error evaluating the function,
event, or macro.

This was the error message I receive. I have the database
(about 260 Mbytes) on CD. When I insert the CD in a system
running on Office 2000 the database works properly in all
functions. When I try the same CD at Office 2003 I face
the reported problem.
Therefore I was thinking about a downwards compatibility
problem.
I have no idea how to overcome the problem and appreciate
very much your help.
With best regards
Sieg



-----Original Message-----
A2003 works directly with an A2000 file, so the problem you are experiencing
is not a compatibility one.

What does the "large fault message" say? It may provide clues as to what is
wrong.

Does your code compile? (Compile on Debug menu, from a code window).

There could be a problem with references. Details:
http://members.iinet.net.au/~allenbrowne/ser- 38.html

In Access 2003, you may receive annoying messages that tell you your
database is unsafe every time you open it. Lower your macro security
setting:
Tools | Macro | Security | Low
If you do not see that menu option, right-click the toolbar area, customize,
and reset the Menu Bar. For more information, see:
http://office.microsoft.com/assistance/preview.aspx?
Click to expand...
Click to expand...
AssetID=HP010504321033&CTT=8&Origin=EC011081751033&Product
=

.
Click to expand...
 
Hmm. If you are switching this database back and forth between A2000 and
A2003 and modifying the objects (not just the data), you will probably see
more of this kind of corruption.

It may be worth running a decompile followed by a compact as soon as you
copy it to the A2000 machine. To decompile, enter something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Hi Allen,
Thank you very much for your valuable hints. I'll try
them out on Saturday. I live in Saudi Arabia and there is
Thursday and Friday the weekend. My Laptop at home I left
in Office 2000. Only my computer at work is on Office
2003.
I'll keep you informed.
With regards
Siegfried
-----Original Message-----
Okay, the message can indicate a partially corrupted database. And yes, it
is possible for a partically corrupted database to work in one version and
not in another.

To try to recover it:
1. Open it in Access 2000.

2 Uncheck the boxes under: Tools | Options | General | Name AutoCorrect.

3 Compact the database: Tools | Database Utilties | Compact.

4 Close Access, and decompile a copy of the database by entering something
like this at the command prompt while Access is not running. It is all one
line, and include the quotes:
"c:\Program Files\Microsoft
Click to expand...
office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

5. Open in A2000 again. Open a code window. Remove any references you do not
need. If you are not sure which you need, see:
http://members.iinet.net.au/~allenbrowne/ser-38.html

6. Check that the application compiles. From the code window: Debug |
Compile.

7. Compact again.

8. Make a copy of the mdb file. Open the copy in A2003. Open a code window,
and choose References from the Tools menu. Check that none are marked
"MISSING". Then check that it still compiles.

9. Test.

If that still does not work, try following the 6 steps for the first symptom
Recovering from Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-47.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Hi, Allen,
It is not a matter of the security level. I changed the
level of protection to "Low" but the problem persists.
Here now the fault message:

Microsoft Office Access

The expression On Click you entered as the event property
setting produced the following error: A problem occured
While Microsoft Access was communicating with the OLE
Server or ActiveX control.

*The expression may not result in the name of a macro, the
name of an user-defined function, or [Event Procedure].
*There may have been an error evaluating the function,
event, or macro.

This was the error message I receive. I have the database
(about 260 Mbytes) on CD. When I insert the CD in a system
running on Office 2000 the database works properly in all
functions. When I try the same CD at Office 2003 I face
the reported problem.
Therefore I was thinking about a downwards compatibility
problem.
I have no idea how to overcome the problem and appreciate
very much your help.
With best regards
Sieg




-----Original Message-----
A2003 works directly with an A2000 file, so the problem
you are experiencing
is not a compatibility one.

What does the "large fault message" say? It may provide
clues as to what is
wrong.

Does your code compile? (Compile on Debug menu, from a
code window).

There could be a problem with references. Details:
http://members.iinet.net.au/~allenbrowne/ser- 38.html

In Access 2003, you may receive annoying messages that
tell you your
database is unsafe every time you open it. Lower your
macro security
setting:
Tools | Macro | Security | Low
If you do not see that menu option, right-click the
toolbar area, customize,
and reset the Menu Bar. For more information, see:
http://office.microsoft.com/assistance/preview.aspx?
Click to expand...
AssetID=HP010504321033&CTT=8&Origin=EC011081751033&Product
=
acc2003


message
Dear All,
I programmed a large database (65,000 records) in
MSAccess
2000. I added a lot of event procedures to the forms in
order to display the contents of tables and queries as
desired. Under Office 2000 these procedures work
properly.
Now I changed to Office 2003 and got MSAccess 2003 on my
computer. I had to experience that now these procedures
added to the forms and e.g. text boxes do not work
anymore. When these procedures are called a large fault
message is displayed. The form will be shown without the
data to be filled in by the procedures.
Is there a solution to overcome the problem or is Access
2003 not downwards compatible?
Thanks and best regards
Siegfried
Click to expand...
Click to expand...
Click to expand...
 
Hi Allen,
I tried all advises, decompiled the database in Access
2000, checked at Access 2003 the references, but no
success.
As I opened in Access 2003 the VBA Editor the first time
I found only a black page, no modules.
Then I detected that all procedures have been assigned
to "Administrator". I changed it to "User" and the
procedures and modules became visible.
But that did not solve my problems.
I think now more than before that this is a compatibility
problem.
I will advise my company to come back to Office 2000.
Thanks and regards
Siegfried
-----Original Message-----
Hmm. If you are switching this database back and forth between A2000 and
A2003 and modifying the objects (not just the data), you will probably see
more of this kind of corruption.

It may be worth running a decompile followed by a compact as soon as you
copy it to the A2000 machine. To decompile, enter something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft
Click to expand...
office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Hi Allen,
Thank you very much for your valuable hints. I'll try
them out on Saturday. I live in Saudi Arabia and there is
Thursday and Friday the weekend. My Laptop at home I left
in Office 2000. Only my computer at work is on Office
2003.
I'll keep you informed.
With regards
Siegfried
-----Original Message-----
Okay, the message can indicate a partially corrupted database. And yes, it
is possible for a partically corrupted database to work in one version and
not in another.

To try to recover it:
1. Open it in Access 2000.

2 Uncheck the boxes under: Tools | Options | General | Name AutoCorrect.

3 Compact the database: Tools | Database Utilties | Compact.

4 Close Access, and decompile a copy of the database by entering something
like this at the command prompt while Access is not running. It is all one
line, and include the quotes:
"c:\Program Files\Microsoft
Click to expand...
office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

5. Open in A2000 again. Open a code window. Remove any references you do not
need. If you are not sure which you need, see:
http://members.iinet.net.au/~allenbrowne/ser- 38.html

6. Check that the application compiles. From the code window: Debug |
Compile.

7. Compact again.

8. Make a copy of the mdb file. Open the copy in A2003. Open a code window,
and choose References from the Tools menu. Check that none are marked
"MISSING". Then check that it still compiles.

9. Test.

If that still does not work, try following the 6 steps for the first symptom
Recovering from Corruption
at:
http://members.iinet.net.au/~allenbrowne/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.

Hi, Allen,
It is not a matter of the security level. I changed the
level of protection to "Low" but the problem persists.
Here now the fault message:

Microsoft Office Access

The expression On Click you entered as the event property
setting produced the following error: A problem occured
While Microsoft Access was communicating with the OLE
Server or ActiveX control.

*The expression may not result in the name of a
Click to expand...
macro,
the
name of an user-defined function, or [Event Procedure].
*There may have been an error evaluating the function,
event, or macro.

This was the error message I receive. I have the database
(about 260 Mbytes) on CD. When I insert the CD in a system
running on Office 2000 the database works properly in all
functions. When I try the same CD at Office 2003 I face
the reported problem.
Therefore I was thinking about a downwards compatibility
problem.
I have no idea how to overcome the problem and appreciate
very much your help.
With best regards
Sieg




-----Original Message-----
A2003 works directly with an A2000 file, so the problem
you are experiencing
is not a compatibility one.

What does the "large fault message" say? It may provide
clues as to what is
wrong.

Does your code compile? (Compile on Debug menu, from a
code window).

There could be a problem with references. Details:
http://members.iinet.net.au/~allenbrowne/ser- 38.html

In Access 2003, you may receive annoying messages that
tell you your
database is unsafe every time you open it. Lower your
macro security
setting:
Tools | Macro | Security | Low
If you do not see that menu option, right-click the
toolbar area, customize,
and reset the Menu Bar. For more information, see:
http://office.microsoft.com/assistance/preview.aspx?
Click to expand...
AssetID=HP010504321033&CTT=8&Origin=EC011081751033&Product
=
acc2003


message
Dear All,
I programmed a large database (65,000 records) in
MSAccess
2000. I added a lot of event procedures to the
Click to expand...
forms
in
order to display the contents of tables and queries as
desired. Under Office 2000 these procedures work
properly.
Now I changed to Office 2003 and got MSAccess 2003 on my
computer. I had to experience that now these procedures
added to the forms and e.g. text boxes do not work
anymore. When these procedures are called a large fault
message is displayed. The form will be shown
Click to expand...
without
the
data to be filled in by the procedures.
Is there a solution to overcome the problem or is Access
2003 not downwards compatible?
Thanks and best regards
Siegfried
Click to expand...
Click to expand...


.
Click to expand...
 
Back
Top