Access 2007 vs. Sccess 2003

[Guest]

I have an application that was originally written in ACCESS 2003. It has a
SQL 2005 back end. Once the application was converted to 2007 and the users
started using the 2007 runtime random errors would occur and queries would
work when I would run the application in the IDE but not work when the were
run using the runtime. Is there a document anywhere that explains the
differences between
the 2003 and 2007 runtimes? Additionally, I am really baffled why queries
would work in the IDE and not with the runtime.

 

[Arvin Meyer [MVP]]

Not sure what you are asking here. The IDE stands for Integrated Development
Environment which to drill through the technospeak means the code window
which is common to all VBA applications. Queries are no run in the IDE,
although you can call Select Statements in code. There is no code window in
the runtime and certain wizard code which calls legacy code statements may
not work, like:

DoCmd.DoMenuItem ....

This has been replaced with:

DoCmd.RunCommand ....

Where a menu item was called that doesn't exist (there are no menus per se
in Access 2007, instead there is the Ribbon) you will get an error.

 

[Guest]

To simplify my question if I run the application with FULL ACCESS it works
fine. When it's run with the runtime it generates random errors such as a
simple text box does not have a default value which is supplied on the object
itself. The date shows up when run with the full version but not using the
runtime.

 

[Arvin Meyer [MVP]]

And you are saying that it works in the 2003 runtime, but not the 2007
runtime? Since the code compilation is different, did you converted to the
application to Access 2007, decompile it, compact it a few times, then
recompiled it, before you converted it to the Runtime? If not try doing
that, and please report back so I can post a bug to Microsoft if it still
doesn't work.
Thanks,
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[Guest]

I converted the database to Access 2007 then compiled it. Then I installed
it along with the 2007 runtime on a user's machine and started receiving
errors. When the errors got to be too many we returned the users back to the
2003 version of the app and runtime. Everything is now running fine. I
will take your suggestion and compact and recompile the app and see if that
changes anything. It seems to be bizarre to believe.

 

[Arvin Meyer [MVP]]

Not recompile only. Decompile using the decompile switch:

http://www.mvps.org/access/bugs/bugs0008.htm

and:

http://www.trigeminal.com/usenet/usenet004.asp

After you have compacted, at least once, decompile and compact 2 or 3 more
times, then compile you project again. Michka's article above explains the
reasons. You can also use my code at:

http://www.datastrat.com/Code/DocDatabase.txt

to save all the objects as text files, then rebuild a new database by using
LoadFromText. Drastic, but is beats starting over and usually works if you
can get a database open.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com