Re: Serious Problem with Date in RecordSource

Tech-Archive recommends: Fix windows errors by optimizing your registry

Jose, the crash could be caused by several things, such as:
a) a bad index on the date field;
b) a corruption caused by Name AutoCorrect;
c) a corruption of the VBA code;
d) a bug in A2002/2003 if the form has/is a subform.

To solve:
a): Repair the database: Tools | Database Utilities | Compact/repair.
b): Disable the Name AutoCorrect boxes: Tools | Options | General.
c): Decompile the database.
d): Add a text box to the subform for the field named in LinkChildFields.

Suggested sequence:
================
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

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, 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.

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, and reference ambiguities are
resolved.

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.

"José António Silva" <JosAntnioSilva@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:62B303DC-CB78-4BD0-B9F9-BD798C54A8D0@xxxxxxxxxxxxxxxx
> Anybody knows the reason Access 2003 crashes when I filter data in a form
> with a date field?
>
> I'm setting the recordsource to: SELECT Guia.* FROM guia WHERE
> Guia.InsertionDate = #7/28/2004#
>
> I also have tried #2004-07-28# but the crash remains.
>
> Table Guia is a linked ODBC table to SQL 2000.


.

Relevant Pages

  • Re: Odd Events
    ... Compact after deleting the bad form, before importing it again from an ... Decompile can help with the kind of corruption you described. ... Compact the database to get rid of this junk: ...
    (microsoft.public.access.formscoding)
  • Re: DoCmd.OpenReport suddenly failing, macro print prints same report ok
    ... This sounds like the kind of corruption that a decompile could fix. ... Compact the database to get rid of this junk: ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.reports)
  • Re: Invalid Argument, Please help!
    ... Here is a post on fixing corruption from Allen Browne. ... Compact the database: ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.formscoding)
  • Re: Why am I getting this Error?
    ... > database, so I'm going to suggest a sequence to try to rescue it. ... Decompile the database by ... Open Access, and compact again. ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.formscoding)
  • Re: Saving form changes hangs.
    ... Compact the database to get rid of this junk: ... Uncheck any references you do not need. ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.formscoding)