Re: Access 2003 with SP3 causing problems
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Thu, 27 Sep 2007 12:19:05 +0800
There are a couple of bugs in Office 2003 SP3, and I've listed them in a yellow div at the top of this page:
http://allenbrowne.com/tips.html
But your description doesn't sound like those. Sounds more like a problem related to a bad binary (needs decompile), possibly connected to Name AutoCorrect.
Here's a standard sequence to try. Work through them in order:
1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html
2. Compact the database to get rid of this junk:
Tools | Database Utilities | 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.
"Viasys" <googlegroups@xxxxxxxxxxxx> wrote in message
news:1190823614.363035.116120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Sep 25, 1:39 pm, "Allen Browne" <AllenBro...@xxxxxxxxxxxxxx> wrote:Viasys, can you provide some more info?
Do these forms have combo boxes on them?
Is the RowSource of the combo a table or a query?
How many fields in the table/query?
Anything in the Format property of the fields in the RowSource table?
Hi Allen, sounds like you know something :-)
Looking at one of the forms now, there's one combo box that uses a SQL
statement against a table.
Rowsource = SELECT [zstblWhatsNew].[WhatsNewID], [zstblWhatsNew].
[VersionNumber], [zstblWhatsNew].[ReleaseDate] FROM [zstblWhatsNew]
No formatting in the combo box or the source table. The form does not
open in design mode either.
Another form I just looked at is a template one I use for unbouind
forms, it has 7 buttons, 4 labels and a box. All the buttons have a
function call (=Functionname(form) or some such) and are no different
to all the other forms that do work. In fact, everything on tjhis
template form would exist in the other forms, which makes it hard to
narrow down. There is a smart tag saying one of the button's short cut
key is used more than once but that doesn't occur i nthe other form
that I looked at.
Now (I purposely re-applied SP3 to a machine) if I try opening in code
in normal mode I get "The microsoft jet database engine cannot find
object '', make sure the obect exists and you spell its name and thre
path name correctly", opening in design view gives the "not enough
memory".
.
- Follow-Ups:
- Re: Access 2003 with SP3 causing problems
- From: Viasys
- Re: Access 2003 with SP3 causing problems
- References:
- Access 2003 with SP3 causing problems
- From: Viasys
- Re: Access 2003 with SP3 causing problems
- From: Allen Browne
- Re: Access 2003 with SP3 causing problems
- From: Viasys
- Access 2003 with SP3 causing problems
- Prev by Date: Re: Database design
- Next by Date: Re: Upsizing Access 2003 db with SourceSafe 6.0d to SQL Server 2005 - Crashes
- Previous by thread: Re: Access 2003 with SP3 causing problems
- Next by thread: Re: Access 2003 with SP3 causing problems
- Index(es):
Relevant Pages
|