PACALA_BA said:
Hi, Thank you.
But in last month
100 OFFICCE-CRASHES Reported to MICROSOFT.....
from my PC-eMAIL: (e-mail address removed)
***********************************
You quoted the following, but you still didn't say to whom (what e-mail
address) at Microsoft you were addressing your e-mails "OFFICE-CRASHES" nor
did you indicate that you opened a service incident with product support.
If, indeed, there are compiler errors, that is what you _must_ do to
initiate the process of obtaining a correction. You did not indicate what
response you received from Microsoft. The procedures for obtaining service
from Microsoft vary by region, and I do not know what they are in your
region, but the following seems to be a general procedure, worldwide:
I would advise that you start at
http://office.microsoft.com, and on the
first/home page, click on "Help and How-To", then on the page that opens
scroll down until you see, in the leftmost column, "Product Support". Click
on "Product Support". A page will open listing the various editions of
Office for which support can be obtained from Microsoft... under the
particular edition/version of Office, choose the version of Access with
which you are having problems. If I choose "Access 2003", that takes me to
the page "Access 2003 Solution Center" which offers many options for
obtaining information and support (most of them free), but if you have
researched those and you have found no help, in the upper right hand corner,
there is a link "Need More Help?" which will lead you through the process of
how to "Contact a Support Professional by Email, Online, or Phone". If you
do so, and what you are reporting is determined to be a product defect, the
charge for the support call will be refunded. If it is determined not to be
a product defect, but due to user actions, then there will be a charge for
the support incident.
Albert Einstein is quoted as saying, "The definition of insanity is
repeating the same action over and over and expecting a different result."
If you got no response from an appropriate organization at Microsoft, a
hundred tries should be enough to convince you that you should change your
approach.
You didn't say how you were reporting the problem to Microsoft... if using
the MsgBox to "send a report to Microsoft" -- those are used for determining
areas of concentration for future releases. They are NOT for initiating
help incidents. You would need to use the normal channels for obtaining
paid service (and I agree, it is not inexpensive) from Microsoft. If,
indeed, they determine that your problem is a product defect, not an error
on your part, your payment will be refunded.
I believe I also explained that the information you provided is insufficient
for anyone to even _guess_ what your problem is, much less to diagnose it,
and even less to assist you in solving it. Allen gave you some suggestions.
If you believe you have exhausted all the possibilities of correcting this
using free support, and are unalterably opposed to taking a chance on paid
support (my guess would be that, for a database application of this size,
you have invested more than enough time and effort to warrant opening a paid
support incident), that it is time to uninstall Access (or all of Office),
reinstall it, make certain you have all the Service Packs for your version,
and try again.
Again, I will repeat -- it is not the size of your database application that
is causing your problem. Your database is not "small" but, it does not come
_near_ straining the limit of total database size (for Access 2000 and
later, a single database can be as large as 2 gigabytes). You might be at
the limit for some object within the database, for example, there is a
maximum number of controls during the lifetime of a form or report -- though
you can work around it if you encounter it. You could, of course, be
experiencing database corruption, and there are steps that can be taken to
try to correct that, as well -- but sometimes all of those steps are not
enough, which would mean you have to go back to a backup copy that works,
and re-start from that working copy.
I am sorry that you are experiencing these difficulties, and I would be
delighted if someone in this newsgroup could help you. But yet another
repetition that you have reported the crashes to Microsoft a hundred times
will not provide anyone enough information to even begin to help. Finally,
helpful as we try to be, all the answers here are from _volunteers_, and our
time and energy are limited -- we are unable to devote the time and energy
to a problem that Microsoft Product Support can devote. Newsgroups are
useful for providing specific answers to specific problems that can be
described, and the description of which is "precise and concise".
Larry Linson
Microsoft Office Access MVP
