If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Queries with Expressions cause a Compile Error
I have a database with many tables and queries, which I have been developing
for several months now. Today, all of the queries which contain at least one expresion started generating a compile error. I have not made any recent changes to most of these queries, and they all refernce different tables. The queries which only have simple field references still work fine (including crosstab and union queries), but anything with anything more than a simple reference (example: [Name]&IIF(IsNull([Title]),"",[Title]) ) generates a compile error. The exact text of the error text box is: Compile error. in query expression '{the full text of the first query expression in the query}'. Any ideas what this could be? I'm using Microsoft Access 2000 (9.0.6926 SP-3). |
#2
|
|||
|
|||
On Mon, 12 Sep 2005 13:20:16 -0700, Dr Rubick
wrote: I have a database with many tables and queries, which I have been developing for several months now. Today, all of the queries which contain at least one expresion started generating a compile error. I have not made any recent changes to most of these queries, and they all refernce different tables. This appears to be the very common References bug. Open any module in design view, or open the VBA editor by typing Ctrl-G. Select Tools... References from the menu. One of the ..DLL files required by Access will probably be marked MISSING. Uncheck it, recheck it, close and open Access. If none are MISSING, check any reference; close and open Access; then uncheck it again. This will force Access to relink the libraries. John W. Vinson[MVP] |
#3
|
|||
|
|||
I did what you said, but it had no effect that I could see. None of the
references were "Missing", so I added one more in, closed and reopened Access (the problem was still there), removed the new refernce, and closed and opened access again (and the problem was still there). "John Vinson" wrote: On Mon, 12 Sep 2005 13:20:16 -0700, Dr Rubick wrote: I have a database with many tables and queries, which I have been developing for several months now. Today, all of the queries which contain at least one expresion started generating a compile error. I have not made any recent changes to most of these queries, and they all refernce different tables. This appears to be the very common References bug. Open any module in design view, or open the VBA editor by typing Ctrl-G. Select Tools... References from the menu. One of the ..DLL files required by Access will probably be marked MISSING. Uncheck it, recheck it, close and open Access. If none are MISSING, check any reference; close and open Access; then uncheck it again. This will force Access to relink the libraries. John W. Vinson[MVP] |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How To Change default error messages | Rich1234 | Using Forms | 7 | March 28th, 2006 12:54 AM |
Any idea why a working query now produces "Compile Error" | SherryT | Running & Setting Up Queries | 3 | September 3rd, 2005 11:35 AM |
Union Queries on ODBC (V FoxPro) linked tables generate error from .mdb front end. | Michael Edwards | Running & Setting Up Queries | 7 | February 26th, 2005 06:29 PM |
Visual Basic Error Messages in Office Apps | Paul Jordan | General Discussions | 2 | August 6th, 2004 03:49 PM |
Continual Error 1321 Trying to Install Office 2003 | Chad Harris | General Discussions | 9 | June 11th, 2004 08:19 AM |