473,387 Members | 1,757 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,387 software developers and data experts.

Access Crashes When Rt Click Build in Query Design View

I'm running Access 2003, modifying a query that has over 45 fields. When I
right click on the field name in Query Design View, and then click Build,
Access crashes before the Build window appears. It doesn't happen every time,
and using the Zoom window works fine. It appears that it only happens when I
want to modify an existing expression. This continues to happen even after
the database is repaired and reopened. Anyone have any suggestions?

--
Message posted via http://www.accessmonster.com

Apr 27 '07 #1
3 7726
Not sure what's causing the problem, but here's a sequence that addresses a
number of issues.

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
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:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
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. Open your query in SQL View.
Copy the query statement out to (say) Notepad.
Close. Then delete the query.
Compact again.
Create a new query.
Paste the query statement from Notepad into SQL View.
Switch to Design view, and tidy it up.

BTW, after setting a property, *always* press Enter before you do anything
else. Do not leave the cursor in the same property and try to test the query
or close the properties box, or ...

Let us know how you went.

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

"mnjkahn via AccessMonster.com" <u27308@uwewrote in message
news:7156d89e81930@uwe...
I'm running Access 2003, modifying a query that has over 45 fields. When
I
right click on the field name in Query Design View, and then click Build,
Access crashes before the Build window appears. It doesn't happen every
time,
and using the Zoom window works fine. It appears that it only happens
when I
want to modify an existing expression. This continues to happen even
after
the database is repaired and reopened. Anyone have any suggestions?
Apr 28 '07 #2
Sorry, Allen, but it didn't work. I thought you had something there for a
moment. When I checked the references I noticed that the ADO library was
Version 2.1. Since I was using Access 2003, and working with an Access 2002-
2003 format database, I changed the reference to 2.5. It worked a few times,
then crashed just like it always had. Now, all I have to do is click Build
on a field, modify it or just select and copy, close the Build, hit enter,
then click on another field and then Build, and I get a crash every time.
And it will happen on more than one query in the database. I have even
created a new database, copied over the linked tables and queries, and had it
crash on the Build.
The query pulls data through 3 queries with data originating from 3 tables
linked to Excel spreadsheets, one of which contains over 75,000 records. I
wouldn't think that either the size, or the fact that I'm using linked Excel
spreadsheets would make a difference, at least it hasn't under Access 2002.
However, at this point, I'm at a loss to explain it.

Here's a little more info, for what its worth:
MS Access 2003(11.6566.8122) SP2
References:
Visual Basic for Applications
Microsoft Access 11.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.5 Library
OLE Automation

Allen Browne wrote:
>Not sure what's causing the problem, but here's a sequence that addresses a
number of issues.

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
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:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
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. Open your query in SQL View.
Copy the query statement out to (say) Notepad.
Close. Then delete the query.
Compact again.
Create a new query.
Paste the query statement from Notepad into SQL View.
Switch to Design view, and tidy it up.

BTW, after setting a property, *always* press Enter before you do anything
else. Do not leave the cursor in the same property and try to test the query
or close the properties box, or ...

Let us know how you went.
>I'm running Access 2003, modifying a query that has over 45 fields. When
I
[quoted text clipped - 6 lines]
>after
the database is repaired and reopened. Anyone have any suggestions?
--
Message posted via http://www.accessmonster.com

May 1 '07 #3
Well, I'm not sure what else to suggest.

Since you disabled Name AutoCorrect and decompiled and compact/repaired and
fixed references and now have fully compiled code and then recreated the
query, I'm not sure what alternatives might help.

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

"mnjkahn via AccessMonster.com" <u27308@uwewrote in message
news:718915f9d099a@uwe...
Sorry, Allen, but it didn't work. I thought you had something there for a
moment. When I checked the references I noticed that the ADO library was
Version 2.1. Since I was using Access 2003, and working with an Access
2002-
2003 format database, I changed the reference to 2.5. It worked a few
times,
then crashed just like it always had. Now, all I have to do is click
Build
on a field, modify it or just select and copy, close the Build, hit enter,
then click on another field and then Build, and I get a crash every time.
And it will happen on more than one query in the database. I have even
created a new database, copied over the linked tables and queries, and had
it
crash on the Build.
The query pulls data through 3 queries with data originating from 3 tables
linked to Excel spreadsheets, one of which contains over 75,000 records.
I
wouldn't think that either the size, or the fact that I'm using linked
Excel
spreadsheets would make a difference, at least it hasn't under Access
2002.
However, at this point, I'm at a loss to explain it.

Here's a little more info, for what its worth:
MS Access 2003(11.6566.8122) SP2
References:
Visual Basic for Applications
Microsoft Access 11.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.5 Library
OLE Automation

Allen Browne wrote:
>>Not sure what's causing the problem, but here's a sequence that addresses
a
number of issues.

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
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:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
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. Open your query in SQL View.
Copy the query statement out to (say) Notepad.
Close. Then delete the query.
Compact again.
Create a new query.
Paste the query statement from Notepad into SQL View.
Switch to Design view, and tidy it up.

BTW, after setting a property, *always* press Enter before you do anything
else. Do not leave the cursor in the same property and try to test the
query
or close the properties box, or ...

Let us know how you went.
>>I'm running Access 2003, modifying a query that has over 45 fields.
When
I
[quoted text clipped - 6 lines]
>>after
the database is repaired and reopened. Anyone have any suggestions?
May 2 '07 #4

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
by: Alicia | last post by:
If I wanted to create a table by hand create table temp( etc, where do I do it in access?
15
by: Pres | last post by:
I am not an experienced programmer. I do have a question regarding workday calculations. I have 3 fields. CURDATE, NUMDAYS, CALCDATE After entering the first two fields, normally the current...
2
by: Ray | last post by:
Stop me if you've heard this, but I am running Access 2002 and all of a sudden, if I design a particular form (it's been working fine for ages), Access crashes rather than open it in design view. ...
0
by: jphelan | last post by:
I have a subform that works fine until you import it into a new database when it crashes if you try to open it in either disign or form view. The form, "Attendees_Subform" in my application was...
6
by: fumanchu | last post by:
I've got to let end users (really just one person) load billing batch files into a third party app table. They need to specify the billing cycle name, the batch name, and the input file name and...
13
by: royaltiger | last post by:
I am trying to copy the inventory database in Building Access Applications by John L Viescas but when i try to run the database i get an error in the orders form when i click on the allocate...
17
by: Mell via AccessMonster.com | last post by:
Is there a way to find out where an application was created from? i.e. - work or home i.e. - if application sits on a (work) server/network, the IT people know the application is sitting...
3
by: Mike | last post by:
Hi, Im trying to create a crosstab query with fewer than 255 headings (about 50), but it crashes when I try to save after writing the heading names in the query property "column headings". My...
8
by: babyangel43 | last post by:
Hello, I have a query set up in Access. I run it monthly, changing "date of test". I would like this query to be merged with a Word document so that the cover letter is created in Word, the fields...
0
by: taylorcarr | last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: aa123db | last post by:
Variable and constants Use var or let for variables and const fror constants. Var foo ='bar'; Let foo ='bar';const baz ='bar'; Functions function $name$ ($parameters$) { } ...
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
1
by: Sonnysonu | last post by:
This is the data of csv file 1 2 3 1 2 3 1 2 3 1 2 3 2 3 2 3 3 the lengths should be different i have to store the data by column-wise with in the specific length. suppose the i have to...
0
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
0
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
0
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.