I'm not an Access programmer, but I thought perhaps I could get some
information here. We have a database that was written in 1992 and has
worked perfectly through the various updates through Access 2003. When
trying to run it under Access 2007, many errors occur. Without going into
excessive detail, it will come up, but most controls will not work.

Is there any listing or any helpful information anyone can give us, to let
us know, what kinds of problems will cause a database that runs under Access
2003 to fail under Access 2007?

Jim

I think you would do well to get an Access programmer to make the update,
but if lots of things fail to work, missing references would be a good place
to start looking. Search google for MS Access missing VBA references, or
open any code module and then in the code editor go to Tools, References and
see if any of the checked references at the top of the list are marked as
missing.

"Jim Gainsley" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm not an Access programmer, but I thought perhaps I could get some
> information here. We have a database that was written in 1992 and has
> worked perfectly through the various updates through Access 2003. When
> trying to run it under Access 2007, many errors occur. Without going into
> excessive detail, it will come up, but most controls will not work.
>
> Is there any listing or any helpful information anyone can give us, to let
> us know, what kinds of problems will cause a database that runs under
> Access 2003 to fail under Access 2007?

You may have a problem with references:
http://allenbrowne.com/ser-38.html

You may need to tell Access 2007 that your database is in a trusted
location. Add your folder under:
Office Button | Access Options | Trust Center | Trust Center Settings

If it compiles fine, and is in a trusted location, it may need a decompile.
Here's a standard sequence for rescuing a problem database:

1. Uncheck the boxes under:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile 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"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

7. Still in the code window, choose Options on the Tools menu. On the
General tab, make sure Error Trapping is set to:
Break on Unhandled Errors
and the Compile on Demand is unchecked.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
the code syntax is compilable, and the VBA options are set to show errors
and avoid this kind of corruption.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/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.

"Jim Gainsley" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm not an Access programmer, but I thought perhaps I could get some
> information here. We have a database that was written in 1992 and has
> worked perfectly through the various updates through Access 2003. When
> trying to run it under Access 2007, many errors occur. Without going into
> excessive detail, it will come up, but most controls will not work.
>
> Is there any listing or any helpful information anyone can give us, to let
> us know, what kinds of problems will cause a database that runs under
> Access 2003 to fail under Access 2007?
>
> Jim

Thanks very much for your pointers.

"Paul Shapiro" <(E-Mail Removed)> wrote in message
news:eL11v%(E-Mail Removed)...
>I think you would do well to get an Access programmer to make the update,
>but if lots of things fail to work, missing references would be a good
>place to start looking. Search google for MS Access missing VBA references,
>or open any code module and then in the code editor go to Tools, References
>and see if any of the checked references at the top of the list are marked
>as missing.
>
> "Jim Gainsley" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm not an Access programmer, but I thought perhaps I could get some
>> information here. We have a database that was written in 1992 and has
>> worked perfectly through the various updates through Access 2003. When
>> trying to run it under Access 2007, many errors occur. Without going into
>> excessive detail, it will come up, but most controls will not work.
>>
>> Is there any listing or any helpful information anyone can give us, to
>> let us know, what kinds of problems will cause a database that runs under
>> Access 2003 to fail under Access 2007?
>
>

Thanks very much. I know about the new security model. We now have an
access programmer and I'll give him your words.

Jim



"Allen Browne" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> You may have a problem with references:
> http://allenbrowne.com/ser-38.html
>
> You may need to tell Access 2007 that your database is in a trusted
> location. Add your folder under:
> Office Button | Access Options | Trust Center | Trust Center Settings
>
> If it compiles fine, and is in a trusted location, it may need a
> decompile. Here's a standard sequence for rescuing a problem database:
>
> 1. Uncheck the boxes under:
> Office Button | Access Options | Current Database | Name AutoCorrect
> Explanation of why:
> http://allenbrowne.com/bug-03.html
>
> 2. Compact the database to get rid of this junk:
> Office Button | Manage | Compact/Repair
>
> 3. Close Access. Make a backup copy of the file. Decompile 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"
>
> 4. Open Access (holding down the Shift key if you have any startup code),
> and compact again.
>
> 5. Open a code window.
> Choose References from the Tools menu.
> Uncheck any references you do not need.
> For a list of the ones you typically need in your version of Access, see:
> http://allenbrowne.com/ser-38.html
>
> 6. Still in the code window, choose Compile from the Debug menu.
> Fix any errors, and repeat until it compiles okay.
>
> 7. Still in the code window, choose Options on the Tools menu. On the
> General tab, make sure Error Trapping is set to:
> Break on Unhandled Errors
> and the Compile on Demand is unchecked.
>
> At this point, you should have a database where the name-autocorrect
> errors are gone, the indexes are repaired, inconsistencies between the
> text- and compiled-versions of the code are fixed, reference ambiguities
> are resolved, the code syntax is compilable, and the VBA options are set
> to show errors and avoid this kind of corruption.
>
> If it is still a problem, the next step would be to get Access to rebuild
> the database for you. Follow the steps for the first symptom in this
> article:
> Recovering from Corruption
> at:
> http://allenbrowne.com/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.
>
> "Jim Gainsley" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm not an Access programmer, but I thought perhaps I could get some
>> information here. We have a database that was written in 1992 and has
>> worked perfectly through the various updates through Access 2003. When
>> trying to run it under Access 2007, many errors occur. Without going into
>> excessive detail, it will come up, but most controls will not work.
>>
>> Is there any listing or any helpful information anyone can give us, to
>> let us know, what kinds of problems will cause a database that runs under
>> Access 2003 to fail under Access 2007?
>>
>> Jim
>