J
Jeff K
Ever since upgrading to Access 2002, I have had the same
problem referencing an external Access database compiled
as an mde. I use the mde as a code library. It never
caused any problems in 2000 but for the last year of
programming in 2002 the following has always happened:
When first opening a database with a reference to the mde,
any time I type "Dim VariableName As . . ." and hit the
space bar, I get the "sorry Access has to close . . ."
before the variable type list shows up.
However, if I first make a meaningless change to the
module, then compile and save, then try to type something
that generates the variable type list, the list shows up
fine. . . until . . .
Now all of a sudden in any NEW database, referencing the
mde, which has had a few changes made over the last year,
I can't do anything that would cause the variable type
list to show up or it crashes. I can program fine in
databases that have existed for a while and have a
reference to the SAME mde but any new one always crashes.
I keep an mdb copy of the code library and referencing
that file will allow me to open the variable type list,
but I have to do my trick of compiling first. I am
getting by now by changing any new database reference to
use the mdb instead of the mde, but it still does the
initial crash if I don't change and compile first, and I
don't want other developers to see the code in the library!
I have a few dozen databases now using the mde with the
following characteristics. They all work fine referencing
the same file that is causing new databases to crash when
programming in them:
-Access Version 2002
-All secured (including the mde) with the same security
file
-mde and individual front-ends installed locally on each
PC (I have tried it with network front-ends too and got
the same result)
-This is happening with every developer in my group, not
just on my PC
-I have all the latest service packs for Office XP and the
newest Jet patch
-Windows 98 OS - I know
-I've sent the error report to Microsoft 100+ times.
I am at my limit with this thing - I've wasted so much
time trying to work around this the past year I wish we
never upgraded. Can anyone help?
problem referencing an external Access database compiled
as an mde. I use the mde as a code library. It never
caused any problems in 2000 but for the last year of
programming in 2002 the following has always happened:
When first opening a database with a reference to the mde,
any time I type "Dim VariableName As . . ." and hit the
space bar, I get the "sorry Access has to close . . ."
before the variable type list shows up.
However, if I first make a meaningless change to the
module, then compile and save, then try to type something
that generates the variable type list, the list shows up
fine. . . until . . .
Now all of a sudden in any NEW database, referencing the
mde, which has had a few changes made over the last year,
I can't do anything that would cause the variable type
list to show up or it crashes. I can program fine in
databases that have existed for a while and have a
reference to the SAME mde but any new one always crashes.
I keep an mdb copy of the code library and referencing
that file will allow me to open the variable type list,
but I have to do my trick of compiling first. I am
getting by now by changing any new database reference to
use the mdb instead of the mde, but it still does the
initial crash if I don't change and compile first, and I
don't want other developers to see the code in the library!
I have a few dozen databases now using the mde with the
following characteristics. They all work fine referencing
the same file that is causing new databases to crash when
programming in them:
-Access Version 2002
-All secured (including the mde) with the same security
file
-mde and individual front-ends installed locally on each
PC (I have tried it with network front-ends too and got
the same result)
-This is happening with every developer in my group, not
just on my PC
-I have all the latest service packs for Office XP and the
newest Jet patch
-Windows 98 OS - I know
-I've sent the error report to Microsoft 100+ times.
I am at my limit with this thing - I've wasted so much
time trying to work around this the past year I wish we
never upgraded. Can anyone help?