|
 |
access thread: Access XP Bombs During Query Design
Message #1 by "Bob Orta" <boborta@r...> on Fri, 26 Jul 2002 08:23:21 -0700
|
|
My system information: Office XP, Access 2000 file format, HP OmniBook,
750 MHz, 256 MB Ram, Win98 SE, XP service pack 2.
I receive an error that states that Access will close and I may
optionally choose to repair the mdb and/or send an error report to Bill
Gates. Here the condition when the bomb goes off:
It occurs at least once/day while testing code (sql queries) under the
following conditions:
I am in the step mode as the code executes and code has created a sql
statement. I go to the immediate window and type '?sql', copy the
result to the clipboard, open a new query and paste the clipboard into
the SQL view (I am ensuring the query statement is correct), and examine
it in the GRID mode. I am not executing the query, only examining it in
the GRID. The BOMBING happens before I click GRID and not always.
Has anyone else had this problem?
Thanks,
Bob
UofA
Message #2 by "Amy Wyatt" <amyw@c...> on Tue, 30 Jul 2002 14:23:58
|
|
Don't actually have an answer for you but I experienced a similar problem
with Access 2000. A month later and $245.00 to microsoft (who were really
no help) I found that having Access 2000 and VB6 on my computer caused my
database objects to arbitrarily become corrupt when debugging code. It did
not happen when using Access 97 on the same database, same computer. I
suspect that it has to do with the fact that 97 does not use the VB editor
and 2000 does.
It was bizzare and I really have no hard evidence that is was the problem
other than it happened consistantly when I had both loaded on my computer
and stopped happening when I reloaded without VB6. Since AccessXP is very
similar to Access 2000 in structure this could be your problem also.
Just a thought,
Amy
> My system information: Office XP, Access 2000 file format, HP OmniBook,
750 MHz, 256 MB Ram, Win98 SE, XP service pack 2.
I receive an error that states that Access will close and I may
optionally choose to repair the mdb and/or send an error report to Bill
Gates. Here the condition when the bomb goes off:
It occurs at least once/day while testing code (sql queries) under the
following conditions:
I am in the step mode as the code executes and code has created a sql
statement. I go to the immediate window and type '?sql', copy the
result to the clipboard, open a new query and paste the clipboard into
the SQL view (I am ensuring the query statement is correct), and examine
it in the GRID mode. I am not executing the query, only examining it in
the GRID. The BOMBING happens before I click GRID and not always.
Has anyone else had this problem?
Thanks,
Bob
UofA
|
|
 |