Microsoft access has encountered a problem .......

[Bob Darlington]

I have been getting the above error message intermittently when I open any
one of five or six forms in design view, change some control formatting
(like backcolor) and try to open the form in form view.
The application is closed down, and when I reopen it, all changes have been
saved, and all appears well.
It makes no difference if I select the option to repair & backup etc or not.
I usually opt to send the error report (if only out of spite).
Is anyone else having similar problems?

--
Bob Darlington
Brisbane

[Trevor Best]

Bob Darlington wrote:

I have been getting the above error message intermittently when I open any
one of five or six forms in design view, change some control formatting
(like backcolor) and try to open the form in form view.
The application is closed down, and when I reopen it, all changes have been
saved, and all appears well.
It makes no difference if I select the option to repair & backup etc or not.
I usually opt to send the error report (if only out of spite).
Is anyone else having similar problems?

What version? Which Service Pack? Does the error reporting bring up a
"More info" link?

--
Pretentious? Moi?

[Bob Darlington]

Access 2002 with SP3 on WinXP SP2.
Yes, there is a more info button, which brings up pages of stuff which may
as well be in Greek.
Next time it comes up (and it is intermittent) I will copy and post it if
you like?

--
Bob Darlington
Brisbane
"Trevor Best" <nospam@localho st> wrote in message
news:41******** *************** @auth.uk.news.e asynet.net...

Bob Darlington wrote:

I have been getting the above error message intermittently when I open
any one of five or six forms in design view, change some control
formatting (like backcolor) and try to open the form in form view.
The application is closed down, and when I reopen it, all changes have
been saved, and all appears well.
It makes no difference if I select the option to repair & backup etc or
not.
I usually opt to send the error report (if only out of spite).
Is anyone else having similar problems?

What version? Which Service Pack? Does the error reporting bring up a
"More info" link?

--
Pretentious? Moi?

[(Pete Cresswell)]

RE/

Is anyone else having similar problems?

My guess is that "Microsoft Access is having a problem..." is too generic for
anybody to say they have or haven't had the same root cause.

Having had it a number of times over the years, my first reaction is that
something is corrupted in the DB.

The first thing I've always done is to rebuild the app by importing all objects
into a new empty DB. Sometimes it's worked, sometimes it has not.

Next step would be to do a series of (undocumented) SaveAsText commands from an
Immediate window and use LoadFromText to pull those modules into a new empty DB.
My guess is that above a certain application size/complexity you could write a
few loops to do this faster than you could do it by hand.
--
PeteCresswell

[Tony Toews]

"(Pete Cresswell)" <x@y.z> wrote:

Next step would be to do a series of (undocumented) SaveAsText commands from an
Immediate window and use LoadFromText to pull those modules into a new empty DB.
My guess is that above a certain application size/complexity you could write a
few loops to do this faster than you could do it by hand.

Sample code at http://www.datastrat.com/Code/DocDatabase.txt

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Trevor Best]

Bob Darlington wrote:

Access 2002 with SP3 on WinXP SP2.
Yes, there is a more info button, which brings up pages of stuff which may
as well be in Greek.
Next time it comes up (and it is intermittent) I will copy and post it if
you like?

The fact you have a more info button would suggest that there is an
update available for Access, visit http://officeupdate.microsoft.com and
check for updates, like WindowsUpdate you'll need IE to do it.

I would follow Pete's suggestion of importing everything into a new db,
see if that helps first.

In the meantime, keep sending those error reports to MS, they do take
notice of them. I had regular problems like this with Access 2002 SP2,
my error reports caused me to get into dialog with one of the developers
and SP3 fixed my problem.

--
Pretentious? Moi?

[Tony Toews]

Trevor Best <nospam@localho st> wrote:

In the meantime, keep sending those error reports to MS, they do take
notice of them. I had regular problems like this with Access 2002 SP2,
my error reports caused me to get into dialog with one of the developers
and SP3 fixed my problem.

MS very much pays attention to those error reports. They love them. Their number
one goal on SPs is to fix those errors where the software crashes. MS personnel
knows how much pain is caused when you lose files and work you've already done.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Bob Darlington]

Thanks Trevor,
The most recent update (apart from 2 security patches) is SP3, which I
already have installed.

The error dialog is pretty standard, and has a hyperlink:
'To see what data this error report contains Click here'
The is no 'More info' button.
The error report cannot be copied, and runs to what looks like hundreds of
pages.

I'll take your advice and keep sending the error reports.

I have only recently imported all objects into a new db to solve a different
problem.

--
Bob Darlington
Brisbane
"Trevor Best" <nospam@localho st> wrote in message
news:41******** *************** @auth.uk.news.e asynet.net...

Bob Darlington wrote:

Access 2002 with SP3 on WinXP SP2.
Yes, there is a more info button, which brings up pages of stuff which
may as well be in Greek.
Next time it comes up (and it is intermittent) I will copy and post it if
you like?

The fact you have a more info button would suggest that there is an update
available for Access, visit http://officeupdate.microsoft.com and check
for updates, like WindowsUpdate you'll need IE to do it.

I would follow Pete's suggestion of importing everything into a new db,
see if that helps first.

In the meantime, keep sending those error reports to MS, they do take
notice of them. I had regular problems like this with Access 2002 SP2, my
error reports caused me to get into dialog with one of the developers and
SP3 fixed my problem.

--
Pretentious? Moi?

[Bob Darlington]

Thanks Tony and Pete.
I'll give that a go.

--
Bob Darlington
Brisbane
"(Pete Cresswell)" <x@y.z> wrote in message
news:c4******** *************** *********@4ax.c om...

RE/

Is anyone else having similar problems?

My guess is that "Microsoft Access is having a problem..." is too generic
for
anybody to say they have or haven't had the same root cause.

Having had it a number of times over the years, my first reaction is that
something is corrupted in the DB.

The first thing I've always done is to rebuild the app by importing all
objects
into a new empty DB. Sometimes it's worked, sometimes it has not.

Next step would be to do a series of (undocumented) SaveAsText commands
from an
Immediate window and use LoadFromText to pull those modules into a new
empty DB.
My guess is that above a certain application size/complexity you could
write a
few loops to do this faster than you could do it by hand.
--
PeteCresswell

[Bob Darlington]

Progress report.
Used SaveasText etc, and so far so good. Haven't had the message recur.
Thanks again for the help.

--
Bob Darlington
Brisbane
"(Pete Cresswell)" <x@y.z> wrote in message
news:c4******** *************** *********@4ax.c om...

RE/

Is anyone else having similar problems?

My guess is that "Microsoft Access is having a problem..." is too generic
for
anybody to say they have or haven't had the same root cause.

Having had it a number of times over the years, my first reaction is that
something is corrupted in the DB.

The first thing I've always done is to rebuild the app by importing all
objects
into a new empty DB. Sometimes it's worked, sometimes it has not.

Next step would be to do a series of (undocumented) SaveAsText commands
from an
Immediate window and use LoadFromText to pull those modules into a new
empty DB.
My guess is that above a certain application size/complexity you could
write a
few loops to do this faster than you could do it by hand.
--
PeteCresswell